Infrastructure coordinated media access control address assignment

ABSTRACT

Described herein are systems, devices, techniques and products for managing the dynamic assignment of media access control (MAC) addresses to wireless network devices, such as by identifying a dynamically assigned MAC address before, after, or during a wireless association process and communicating the dynamically assigned MAC address to a wireless network device. Also disclosed are systems, devices, techniques and products for preventing a denial of service attack on a wireless access point&#39;s association table, such as by requiring devices that associate with a wireless access point to respond to a query from the wireless access point shortly after association.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of and is a continuation ofco-pending U.S. application Ser. No. 14/792,313 filed on Jul. 6, 2015,which is hereby expressly incorporated by reference in its entirety forall purposes.

FIELD

The present disclosure generally relates to technologies for managingcomputer networks. Specifically, various techniques and systems areprovided for managing addressing of wireless clients connected towireless networks.

BACKGROUND

A media access control (MAC) address is an identifier assigned to anetwork interface of a computing device to allow for low level (e.g.,layer 2 or data link layer in the Open Systems Interconnection model)communications between devices on a shared network medium. Institute ofElectrical and Electronics Engineers (IEEE) networking specifications,such as IEEE 802.3 (Ethernet) and IEEE 802.11 (Wi-Fi), define variousaspects of the physical and data link layers, including media accesscontrol. Among other uses, MAC addresses are used in header informationof network messages to facilitate transmission from a source device to adestination device. For example, layer 2 frames may include a source MACaddress and a destination MAC address.

MAC addresses have been typically treated as unique identifiers. MACaddresses commonly use a 48-bit (6-byte) addressing scheme, though64-bit addresses are also in use. The first 24 bits (3 bytes) of a48-bit MAC address correspond to an Organizationally Unique Identifier(OUI) and the last 24 bits (3 bytes) are specific to the networkinterface. The seventh most significant bit in a MAC address identifiesthe MAC address as a universally administered address or a locallyadministered address. If this bit is 0, the address is a universallyadministered address; if this bit is 1, the address is a locallyadministered address. In the universally administered scheme, the first3 bytes of a MAC address (OUI) corresponds to the device manufacturerand the last 3 bytes are uniquely assigned to individual networkinterface cards.

Every network interface card is typically assigned a universallyadministered MAC address with this address stored in hardware orfirmware of the network interface card. As used herein, the phrases“true MAC address” and “hardware MAC address” are used to refer to theoriginal MAC address of a network interface card that has been assignedby the manufacturer. MAC addresses assigned by the manufacturer areintended to be unique, e.g., the manufacturer is not supposed to assignthe same MAC address to more than one device. A consequence of using thetrue MAC address in network communications is that, because this addressdoes not change and is intended to be unique, devices can be uniquelyand repeatedly identified by other network device based only on theirtrue MAC address.

Mobile device manufacturers have begun masking MAC addresses of wirelessnetwork interfaces at the operating system level for a variety ofreasons and using a variety of techniques. For example, prior toassociation with any wireless access points certain mobile devices canuse a random MAC address generated by the mobile device for transmittedprobe requests. Probe requests are used for scanning for availablewireless access points, and may be considered a one-time use typemessage for which a random MAC address would be suitable. In this way,the probe requests may not uniquely identify the device and thus thedevice's identity may be masked, at least in part. It is possible,however, for a random MAC address to be identical to a MAC address usedby another device, which may result in network problems. Networkproblems or problems with certain network or other functionality alsocan result if a mobile device changes its MAC address during anassociation session or uses different MAC addresses for differentassociation sessions with the network. MAC addresses that are not trueMAC addresses and are generated by a client device may be referred toherein as a “generated” MAC address or a “client generated” MAC address.

SUMMARY

Described herein are systems, devices, techniques, and products forassociating wireless client devices with network devices, such as accesspoints, using an infrastructure assigned media access control (MAC)address. Infrastructure assigned MAC addresses may also be referred toherein as “designated” MAC addresses or “network designated” MACaddresses. Designated MAC addresses are identified by a networkinfrastructure device for a particular wireless client device to usebefore, during, or after an association process so that the wirelessclient device can associate with a network using the designated MACaddress.

Also disclosed are systems, devices, techniques, and products forassociating wireless client devices with network devices, such as accesspoints, in a way that limits the ability of wireless client devices torepeatedly associate with the network device using different MACaddresses and create excessive association table entries.

In an aspect, methods are provided, such as computer implementedmethods. Computer implemented methods of this aspect may be implementedon a network device, such as a network device, network controller,access point, and the like. Computer implemented methods of this aspectmay also be implemented on wireless client devices, such as laptopcomputers, tablet computers, smartphones, printers, and the like. Invarious embodiments, devices for performing methods of this aspect mayinclude network hardware, such as wired and wireless networktransceivers, power supplies, batteries, antennas, physical networkports, etc., and may be configured to wirelessly communicate with otherdevices even if the devices are not associated with a common wirelessnetwork.

Methods of this aspect are optionally performed by network devices, suchas wireless access points, network controllers, network managementdevices, services or appliances, etc. In various embodiments, adesignated MAC address used by a wireless client is determined by anetwork infrastructure device during the association process. In aspecific embodiment, a method of this aspect comprises receiving, at anetwork device, a frame from a wireless client device that includes aMAC address being used by the wireless client device, such as a true orgenerated MAC address; transmitting a response, such as, but not limitedto, an association response that includes an association identifier forthe wireless client device; identifying a designated MAC address for useby the wireless client device; transmitting the designated MAC address;facilitating disassociation with the wireless client device; receiving anew request, such as, but not limited to, a new association request fromthe wireless client device that includes the designated MAC address;transmitting a new response, such as, but not limited to, a newassociation response that includes a new association identifier for thewireless client device; and updating an association table with an entryfor the wireless client device, such as an entry that includes thedesignated MAC address. Optionally, the network device is a wirelessaccess point compliant with an IEEE 802.11 standard.

In embodiments, a frame received from a wireless client device may be arequest, such as an explicit request for a designated MAC address. Inother embodiments, a frame received from a wireless client device maynot correspond to a request at all; that is, it may not be a query forinformation or a response, but may instead simply be another type offrame. For example, a frame received from a wireless client device maybe other than a request for a designated MAC address, such as a wirelessmanagement frame, for example an authentication frame, an associationrequest, etc., a class 1 frame, or a data frame. Optionally, a framereceived from a wireless client device that is not using a designatedMAC address, such as a designated MAC address that may optionally beprovided by the network device, may be treated as if the frame includeda request for a designated MAC address. In this way, network devicesimplementing aspects described herein can receive frames from a wirelessclient device and then transmit a response including a designated MACaddress to be used thereafter by the wireless client device, withoutspecific configuration or operational changes to the wireless clientdevices for requesting the designated MAC address. Upon receiving adesignated MAC address, a wireless client device may advantageouslyadopt and use this designated MAC address for subsequent communicationswith the network device.

In embodiments, methods of this aspect include causing a disassociationbetween a network device, such as an access point, and a wireless clientdevice and then causing a reassociation using an infrastructuredesignated MAC address. Optionally, the disassociation is caused becausethe wireless client device is not using an infrastructure designated MACaddress. For example, in some embodiments, facilitating disassociationincludes transmitting or receiving a disassociation message. The skilledartisan will appreciate that disassociation may be caused by thewireless client device or the network device. Accordingly, facilitatingdisassociation optionally includes transmitting a disassociation frameor a deauthentication frame. Alternatively, facilitating disassociationoptionally includes receiving a disassociation frame or adeauthentication frame. Optionally, facilitating disassociation causesthe wireless client device to transmit a new request or frame includingthe designated MAC address.

Optionally, methods of this aspect do not require a disassociation tooccur between a network device, such as an access point, and a wirelessdevice. For example in one embodiment, a method of this aspect comprisesreceiving, at a network device, a request, such as, but not limited to,an authentication request that is related to a wireless client deviceand that includes a MAC address corresponding to the wireless clientdevice; identifying a designated MAC address for use by the wirelessclient device; transmitting a response, such as, but not limited to, anauthentication response that includes the designated MAC address;receiving a new request, such as, but not limited to, an associationrequest that is related to the wireless client device and that includesthe designated MAC address; transmitting a new response, such as, butnot limited to, an association response that includes an associationidentifier for the wireless client device; and updating an associationtable with an entry for the wireless client device, such as an entrythat includes the designated MAC address. In embodiments, the networkdevice is a wireless access point compliant with an IEEE 802.11standard.

In embodiments, a designated MAC address is a MAC address that isselected by a wireless network infrastructure device or relatedcontroller or network management device or service for use by a wirelessclient device instead of a wireless client device's true or generatedMAC address. For some embodiments, a designated MAC address correspondsto a locally administered address selected by the network infrastructurefor use by a wireless client device, and may optionally be randomly orsystematically selected. As described above, the first 24 bits (3 bytes)of a 48-bit MAC address correspond to an Organizationally UniqueIdentifier (OUI) and the last 24 bits (3 bytes) are specific to thenetwork interface. The seventh most significant bit in a MAC addressidentifies the MAC address as a universally administered address or alocally administered address. If this bit is 0, the address is auniversally administered address; if this bit is 1, the address is alocally administered address. In the universally administered scheme,the first 3 bytes of a MAC address (OUI) corresponds to the devicemanufacturer and the last 3 bytes are uniquely assigned to individualnetwork interface cards. Use of locally administered MAC addresses (inwhich the seventh most significant bit is 1) for designated MAC addressprovides a benefit in that a designated MAC address generally cannot bethe same as a true MAC address used by a wireless client device, as trueMAC addresses generally correspond to universally administered addresses(in which the seventh most significant bit is 0), so there will be, atminimum, a one bit difference between a designated MAC address and theclosest true MAC address. Optionally, a designated MAC addresscorresponds to a locally administered MAC address. In embodiments,designated MAC addresses correspond to random MAC addresses that arelocally administered. Use of locally administered MAC addresses mayprovide advantages in limiting confusion of the designated MAC addressas corresponding to a specific hardware vendor. Use of locallyadministered MAC addresses may also provide advantages in preventing twowireless client devices from using the same MAC address, such as asituation where one wireless client device uses its true MAC address andwhere another wireless client device uses a designated MAC address thatis selected at random.

Other techniques for preventing multiple devices from using the same MACaddress may be implemented. For example, designated MAC addresses may beidentified in which certain bits are unlikely to be used or are not usedby a wireless client device, such MAC addresses including an OUIcorresponding to an obsolete or defunct manufacturer or including an OUIthat is unassigned.

Alternatively or additionally, a list of MAC addresses that have beenobserved and/or identified, including identified or assigned designatedMAC addresses, may be maintained. Optionally, designated MAC addressesnot on the list may be identified for new wireless client devices. Inthis way, new wireless client devices can be assigned designated MACaddresses that are not already in use by another wireless client device.

Alternatively or additionally, the same designated MAC address may beidentified for a wireless client device each time the wireless clientdevice associates with a network or one or more network devicesconnected to the network, such as when the wireless client device roamsor re-associates with the network after some disassociation period. Inthis way, the same designated MAC address can be re-assigned for use bythe wireless client device. Optionally, device characteristics orauthentication characteristics can be used for tracking the wirelessclient device, as will be described in more detail below, to facilitatereidentification of a MAC address previously designated for use by thewireless client device.

Various techniques are useful for identifying the designated MAC addressto be used by the wireless client device. For example, in oneembodiment, identifying includes selecting the designated MAC addressfrom a pool of predetermined MAC addresses available to the networkdevice for use by client devices. Optionally, identifying includesselecting the designated MAC address from a pool of random MAC addressesavailable to the network device for use by client devices. Optionally, adesignated MAC address is identified by the network device. Optionally,a pool of predetermined, random, or designated MAC addresses is assignedto the network device for identification for and assignment to wirelessclient devices. In this way, a network device may receive a block orlist of designated MAC addresses and use addresses from the block orlist for identification of designated MAC addresses to be used bywireless client device.

In some embodiments, a designated MAC address is identified by anothernetwork device, such as a network controller, a network managementdevice, service or appliance, etc. Optionally, the designated MACaddress is identified by a device designated to manage network access.For example, in one embodiment, identifying includes transmitting adesignated MAC address request, such as to another network device, andreceiving the designated MAC address in response. For example, receivingthe designated MAC address request at some other network device causesthe other network device to transmit a designated MAC address responseincluding the designated MAC address. In this way, a network device canadvantageously query another network device for a designated MAC addressfor use by a wireless client device and need not necessarily managedesignated MAC address assignments itself. For example, querying anothernetwork device for a designated MAC address for use by a wireless clientdevice can occur in response to an association attempt by the wirelessclient device or in response to a MAC address request received from thewireless client device.

The designated MAC address may be communicated to the wireless clientdevices using a variety of data exchanges. For example, in oneembodiment, the association response includes transmitting thedesignated MAC address. Optionally, facilitating disassociation includestransmitting the designated MAC address. Optionally, a data message istransmitted by the network device that includes the designated MACaddress.

In various embodiments, a MAC address included in an initial associationrequest is not a true or hardware MAC address of a wireless clientdevice but is instead a generated MAC address, which may correspond to arandom MAC address or a locally administered MAC address. For example,in one embodiment, identifying a designated MAC address includesidentifying the MAC address included in the association request asdifferent from a hardware MAC address corresponding to the wirelessclient device. Optionally, identifying a designated MAC address includesidentifying the MAC address included in the association request as agenerated MAC address. Optionally, identifying a designated MAC addressincludes identifying the MAC address included in the association requestas a randomly assigned MAC address. Optionally, identifying a designatedMAC address includes identifying the MAC address included in theassociation request as a locally administered MAC address. In someembodiments, after identifying the MAC address included in the requestas a locally administered MAC address, the network device transmits adesignated MAC address.

Characteristics of a wireless client device may be useful for trackingthe wireless client device. For example, useful characteristics include,but are not limited to a true or hardware MAC address of the wirelessclient device, a tracking cookie present on the wireless client device,a device identifier corresponding to the wireless client device, adevice profile corresponding to the wireless client device,authentication credentials corresponding to a user of the wirelessclient device, software credentials corresponding to a softwarecomponent present on the wireless client device, a token correspondingto the wireless client device, a token corresponding to a user of thewireless client device, a wireless signature characterizing the wirelesstransmission/reception of the wireless client device, a software profileof the wireless client device, a hardware profile of the wireless clientdevice, and the like. Optionally, a method of this aspect furthercomprises determining a characteristic of the wireless client device;and tracking the wireless client device using the characteristic.

Wireless client device characteristics may be determined through one ormore data exchanges between a network device and a wireless clientdevice. For example, a wireless client device characteristic may betransmitted by the wireless client device, such as during a networkdiscovery or announcement process or through use of one or more networktechnologies, such as Universal Plug and Play, Zero-configurationnetworking, Bonjour, etc. Characteristics may also include wirelessclient device profiles or fingerprints that may identify the wirelessclient device and may be determined by a network device by analysis ofdomain name server requests, hardware characteristics, softwarecharacteristics, network characteristics, wireless broadcastcharacteristics, etc., to allow repeated identification of a wirelessclient device on the network infrastructure side.

Optionally, tracking includes determining a location of the wirelessclient device, such as a physical location or a geographic location.Optionally, the location of the wireless client device is stored and/oranalyzed. Optionally, the location of the wireless client device islinked and/or correlated with a device identifier. Various locationdetermination methods may be incorporated into the methods describedherein, including wireless triangulation methods, proximitydetermination methods, distance determination methods, directiondetermination methods, location determination methods includingbeamforming techniques, etc. Optionally, the location of the wirelessclient device is used for identification of a client device as a clientdevice that has previously associated with or attempted association witha network device.

In embodiments, a designated MAC address may be identified for use by aspecific wireless client device and may be repeatedly assigned to thespecific wireless client device upon later associations with the networkdevice or with other network devices within the same network.Optionally, a designated MAC address is reassigned to the specificwireless client as it roams to neighboring network devices connected tothe same network. Optionally, tracking includes linking the designatedMAC address to the wireless client device, such as through one or moredatabase or table entries. Optionally, linking facilitatesreidentification of the designated MAC address for later use by thewireless client device. For example, an embodiment of this aspect mayfurther comprise determining a characteristic of the wireless clientdevice and linking the designated MAC address with the characteristic ofthe wireless client device, such as to facilitate identification of thedesignated MAC address for use by the wireless client device when thewireless client device associates with another network device.Optionally, identifying the designated MAC address includes determininga characteristic of the wireless client device. Optionally, identifyingthe designated MAC address includes using the characteristic of thewireless client device.

In various embodiments, a network device, such as an access point, mayadvertise network services, such as the ability to provide a designatedMAC address to a wireless client device. In this way, a network devicemay inform wireless client devices that the network device can provide adesignated MAC address or requires the use of true or designated MACaddresses for associating devices. Optionally, a method of this aspectfurther comprises transmitting an indicator of an availability ofdesignated MAC addresses. For example, receiving the indicator at awireless client device facilitates the wireless client devicetransmitting a request for a designated MAC address. Optionally,receiving the indicator at a wireless client device causes the wirelessclient device to transmit a request for a designated MAC address.

As used herein, the term indicator corresponds to a detectable signalproviding a notification. In embodiments, an indicator may correspond toa flag or bit in a data message. Optionally, an indicator may correspondto a recognizable, agreed upon, or standardized sequence included in aframe or other message transmitted by a network device. Optionally,transmitting the indicator includes transmitting a beacon frame or aprobe response frame including the indicator. Optionally, a service setidentifier (SSID) of the beacon frame or probe response frame includesthe indicator. Optionally, a vendor specific element of the beacon frameor probe response frame includes the indicator. Other embodiments arepossible.

Optionally, in some embodiments, a network device may not broadcast theavailability of designated MAC address but still may require use ofdesignated MAC addresses and/or true MAC addresses by wireless clientdevices that associate or attempt to associate with the network device.In one embodiment, a network device may refuse association or otherwisefail to associate with a wireless client device unless the wirelessclient device transmits an association request including a designatedMAC address that has been provided by the network infrastructure.

In some embodiments, upon a wireless client device initially associatingusing a MAC address that is not a designated MAC address or is not atrue MAC address, permission may be requested for use of designated MACaddresses, such as by using an opt-in or opt-out method. For example, inone embodiment, a method of this aspect further comprises transmitting acaptive portal website that requests input authorizing use of adesignated MAC address; and receiving input corresponding to anauthorization to use the designated MAC address.

Embodiments described herein are useful for limiting the creation ofentries in an association table that are not used or may otherwisecreate difficulties for associating additional wireless client deviceswith a network device, such as an access point. In one embodiment, amethod of this aspect further comprises transmitting an associationquery, such as an association query that includes the designated MACaddress; monitoring for a response to the association query for apredetermined time period; determining that no response to theassociation query is received during the predetermined time period; andupdating the association table to remove the entry for the wirelessclient device. Optionally, receiving the association query at thewireless client device causes the wireless client device to transmit aresponse to the association query.

In various embodiments, designated MAC addresses are identified for useby a single wireless client device. In some embodiments, failure toassociate using a designated MAC address within a specified time periodresults in the designated MAC address automatically being released orotherwise designated as unreserved and, thus, available for use byanother wireless client device. In one embodiment, a method of thisaspect further comprises monitoring for an association request includingthe designated MAC address for a predetermined time period; determiningthat no association request including the designated MAC address isreceived during the predetermined time period; and identifying thedesignated MAC address as available for use by another wireless clientdevice. In one embodiment, identification of a designated MAC address asavailable or unavailable includes modification of an entry in a databaseor table.

Optionally, additional authentication processes are required for networkaccess after association. For example, embodiments of this aspectoptionally further comprise facilitating authentication of the wirelessclient device after transmitting the new association response.Alternatively or additionally, embodiments of this aspect furthercomprise determining that the wireless client device has notsuccessfully authenticated within a predetermined time period aftertransmitting the new association response; and updating the associationtable to remove the entry for the wireless client device. Alternativelyor additionally, embodiments of this aspect further comprisetransmitting an authentication query; monitoring for an authenticationresponse to the authentication query for a predetermined time period;determining that no authentication response is received during thepredetermined time period; and updating the association table to removethe entry for the wireless client device. Optionally, receiving theauthentication at the wireless client device causes the wireless clientdevice to transmit a response to the authentication query. In a specificembodiment, the authentication query and the response to theauthentication query include elements of an IEEE 802.1X authenticationprocess. In a specific embodiment, the authentication query and theresponse to the authentication query include elements of an IEEE 802.11iauthentication process.

Methods of this aspect are optionally performed by wireless clientdevices. For example, in a specific embodiment, a method of this aspectcomprises transmitting, by a wireless client device, a frame, such as anassociation request, that includes a media access control (MAC) addresscorresponding to the wireless client device; receiving an associationresponse, such as an association response that is related to a networkdevice and that includes an association identifier; receiving adesignated MAC address; disassociating from the network device;transmitting a new association request to the network device, such as anew association request that includes the designated MAC address; andreceiving a new association response, such as a new association responsethat is related to the network device and that includes a newassociation identifier.

In various embodiments, a wireless client device may include softwarefeatures, specialized applications, or operating system features thatallow for the use of and/or recognize designated MAC addresses andemploy them as described herein. Optionally, security settings on anetwork may activate software features, specialized applications, oroperating system features on the client device that employ the methodsdescribed herein for using designated MAC addresses. For example, in oneembodiment, a software process, such as an operating system or anapplication on the wireless client device, may generate a request for adesignated MAC address or may generate an association request or otherquery that results in identification of a designated MAC address for useby the wireless client device. Optionally, such a software process maybe installed by a device manufacturer or may be part of an operatingsystem installed on the wireless client device. Optionally, such asoftware process may be downloaded and/or installed by a user andavailable through an application store or other software database.Optionally, such a software process may be downloaded and/or installedby an administrator as part of a device, user, or security enrollmentprocess. In some embodiments, such a software process may beincorporated into a network log-on, authentication, or connectionroutine, such as a process for connection to a virtual private network(VPN). In one embodiment, an operating system or application softwarefeature for requesting a designated MAC address may be activated uponinstallation of a security certificate and/or network profile, such asmay be installed and/or downloaded by an administrator as part of adevice, user, or security enrollment process. In such a configuration,upon installation of the security certificate and/or network profile, asoftware feature on a wireless client device may begin requestingdesignated MAC addresses, such as upon associating or detecting awireless network, such as a wireless network that makes use ofdesignated MAC addresses.

As described previously, disassociation may be initiated by the networkinfrastructure or the wireless client device. In one embodiment,facilitating disassociation includes transmitting or receiving adisassociation message. Optionally, facilitating disassociation includestransmitting or receiving a disassociation frame or a deauthenticationframe. Optionally, facilitating disassociation includes receiving thedesignated MAC address.

In embodiments, a network device receiving a request identifies thedesignated MAC address for use by the wireless client device. In oneembodiment, for example, receiving the request at the network devicecauses the network device to identify the designated MAC address.Optionally, the request includes an identifier corresponding to thenetwork device. Optionally, identification of the designated MAC addressincludes using the identifier corresponding to the network device.

Upon receiving the designated MAC address, in embodiments, the wirelessclient device connects with the wireless network using the designatedMAC address. Optionally, the network device that is associating with thewireless client device may verify the designated MAC address used by thewireless client device. For example, receiving an association request atthe network device causes the network device to confirm that thedesignated MAC address included in the association request is authorizedfor use by the wireless client device. Optionally, receiving anassociation request at the network device causes the network device toupdate an association table with an entry for the wireless clientdevice, such as an entry that includes the designated MAC address.

Optionally, methods of this aspect do not require a disassociation tooccur between a network device, such as an access point, and a wirelessdevice. For example in one embodiment, a method of this aspect comprisestransmitting, by a wireless client device, a request, such as, but notlimited to, an authentication request that includes a media accesscontrol (MAC) address corresponding to the wireless client device;receiving a response, such as, but not limited to, an authenticationresponse that is related to a network device and that includes adesignated MAC address; transmitting a new request, such as, but notlimited to, an association request that includes the designated MACaddress; and receiving a new response, such as, but not limited to anassociation response that is related to the network device and thatincludes an association identifier.

Optionally, the wireless client device may determine that the wirelessnetwork is offering or requiring the use of designated MAC addresses.For example, in one embodiment, a method of this aspect furthercomprises receiving an indicator of an availability of designated MACaddresses. Optionally, methods of this aspect further comprisetransmitting a request for a designated MAC address. For example, inembodiments, receiving the request for a designated MAC address at anetwork device causes the network device to identify a designated MACaddress. Optionally, receiving the indicator includes receiving a beaconframe or a probe response frame. Optionally, the beacon frame or proberesponse frame includes the indicator. Optionally, a service setidentifier (SSID) of the beacon frame or probe response frame includesthe indicator. Optionally, a vendor specific element of the beacon frameor probe response frame includes the indicator.

In specific embodiments, an opt-in or opt-out process may be used forproviding the ability to associate with a wireless network using adesignated MAC address. For example, in one embodiment, a method of thisaspect further comprises displaying a captive portal website, whereinthe captive portal website requests input authorizing use of adesignated MAC address; receiving input corresponding to anauthorization to use the designated MAC address; and transmitting theauthorization.

Methods of this aspect may further require an associated device toexchange additional data with the network device shortly afterassociation in order to maintain or create an association table entry onthe network device. Use of such techniques may advantageously minimizethe risk of the association table filling up with erroneous or unusedentries, such as entries corresponding to wireless client devices thathave disconnected from the network device but that did not communicatethis to the network device. As will be understood by the skilledartisan, an association table on a network device, such as a wirelessaccess point, has a finite size, such as a size of 256 entries. If 256entries are present in the association table, additional wireless clientdevices may not be able to associate with the network device. In oneembodiment, a method of this aspect further comprises receiving a query,such as an association query, that includes the designated MAC address;and transmitting a response to the association query.

Optionally, additional authentication after the association processcompletes will be required before a wireless client device can transmitdata through the network. For example, in embodiments, a method of thisaspect further comprises receiving an authentication query; andtransmitting a response to the authentication query. Optionally, ifauthentication is not successfully completed, a network device maydisassociate the unauthenticated wireless client device. For example, inembodiments, receiving the response to the authentication query at thenetwork device causes the network device to update an association tablewith an entry for the wireless client device, such as an entry includesthe designated MAC address. Optionally, the authentication query and theresponse to the authentication query include elements of an IEEE 802.1Xauthentication process. Optionally, the authentication query and theresponse to the authentication query include elements of an IEEE 802.11iauthentication process.

As described above, methods of this aspect are optionally performed bynetwork devices, such as wireless access points, network controllers,network management devices or services or appliances, etc. In variousembodiments, a designated MAC address to be used by a wireless client isdetermined before a wireless client device associates with the networkdevice. For example, a specific method embodiment of this aspectcomprises receiving, at a network device, a request for a media accesscontrol (MAC) address, such as a request that is related to a wirelessclient device; identifying a designated MAC address for use by thewireless client device; transmitting a response to the request thatincludes the designated MAC address; receiving an association request,such as an association request related to the wireless client devicethat includes the designated MAC address; transmitting an associationresponse that includes an association identifier for the wireless clientdevice; and updating an association table with an entry for the wirelessclient device that includes the designated MAC address. As describedabove, network devices may be compliant with a wireless networkstandard, such as an IEEE 802.11 standard, for example, an 802.11nstandard, an 802.11ac standard, and later and future 802.11 standards.

In various embodiments, methods of identifying and communicating adesignated MAC address may occur prior to association. As will beunderstood by the skilled artisan, data exchanges between non-associateddevices are possible, such as those frames which are exchanged duringinitial probing or during the association process. In embodiments, theMAC address request includes a Class 1 management frame, an actionframe, an authentication frame, or a probe request frame. Inembodiments, the response includes a Class 1 management frame, an actionframe, an authentication frame, or a probe response frame. Optionally,transmitting the response to the MAC address request includestransmitting the response to the MAC address request when an entry forthe wireless client device is not present in the association table.

Use of designated MAC addresses is useful for allowing a network tomanage the MAC addresses used by wireless client devices and to trackvarious characteristics of the wireless client devices. Optionally,receiving the designated MAC address at a wireless client device causesthe wireless client device to transmit an association request includingthe designated MAC address. In an embodiment, a method of this aspectfurther comprises confirming that the designated MAC address included inthe association request is authorized for use by the wireless clientdevice.

Various techniques are useful for identifying a designated MAC address.For example, in one embodiment, identifying includes selecting thedesignated MAC address from a pool of predetermined MAC addresses.Optionally, identifying includes selecting the designated MAC addressfrom a pool of random MAC addresses. Optionally, identifying includestransmitting a designated MAC address request, such as to a networkcontroller or other management device, service or appliance, andreceiving the designated MAC address. Optionally, receiving thedesignated MAC address request at a controller causes the controller totransmit a designated MAC address response including the designated MACaddress. Optionally, the controller utilizes a pool of random MACaddresses for the designated MAC addresses, such as a pool includinglocally administered MAC addresses. In this way, the designatedaddresses selected by the controller for a wireless client device can betracked to ensure multiple wireless client devices are not assigned thesame designated MAC address or to ensure that a designated MAC addressis not the same as a true MAC address that may be in use by anotherwireless client device.

Optionally, use of a designated MAC address may be required when a MACaddress used in the MAC address request is determined to be a generatedMAC address or determined to not correspond to a hardware MAC address.For example, in one embodiment, receiving the MAC address requestincludes identifying a MAC address included in the MAC address requestas different from a hardware MAC address corresponding to the wirelessclient device. Optionally, receiving the MAC address request includesidentifying a MAC address included in the MAC address request as aclient generated MAC address. Optionally, receiving the MAC addressrequest includes identifying a MAC address included in the MAC addressrequest as a randomly assigned MAC address. Optionally, receiving theMAC address request includes identifying a MAC address included in theMAC address request as a locally administered MAC address.

As described above, tracking of devices may be advantageous for a numberof reasons, including simplifying roaming of wireless client devicesbetween access points, to allow for location determination, to trackbehavior of the same device over time for diagnostic or networkmanagement purposes, or for reuse/reassignment of designated MACaddresses by/to the same wireless client device. For example, in anembodiment, a method of this aspect further comprises: determining acharacteristic of the wireless client device; and tracking the wirelessclient device using the characteristic. Optionally, tracking includesdetermining a location of the wireless client device. Optionally, adesignated MAC address is determined based on the location of thewireless device at the time the designated MAC address is requestedand/or assigned. Optionally, tracking includes linking the designatedMAC address to the wireless client device to facilitate reidentificationof the designated MAC address for use by the wireless client device.Optionally, a method of this aspect further comprises determining acharacteristic of the wireless client device; and linking the designatedMAC address with the characteristic of the wireless client device tofacilitate identification of the designated MAC address for use by thewireless client device when the wireless client device roams to anotherwireless network device. Optionally, identifying the designated MACaddress includes determining a characteristic of the wireless clientdevice and identifying the designated MAC address using thecharacteristic of the wireless client device.

As described above, the network infrastructure may advertise that it isproviding or requiring designated MAC addresses. For example, in oneembodiment, a method of this aspect further comprises transmitting anindicator of an availability of designated MAC addresses. Optionally,receiving the indicator at a wireless client device facilitates thewireless client device transmitting a request for a MAC address.Optionally, transmitting the indicator includes transmitting a beaconframe or a probe response frame, and wherein the beacon frame or proberesponse frame includes the indicator. In embodiments, a service setidentifier (SSID) of the beacon frame or probe response frame includesthe indicator. In embodiments, a vendor specific element of the beaconframe or probe response frame includes the indicator.

Methods of this aspect may use data exchanges to limit association tabledenial of service attacks in which, for example, a client device usesdifferent client generated MAC addresses in separate associationrequests over a limited period of time. For example, in an embodiment, amethod of this aspect further comprises transmitting an associationquery; monitoring for a response to the association query for apredetermined time period; determining that no response to theassociation query is received during the predetermined time period; andupdating the association table to remove the entry for the wirelessclient device. Optionally, receiving the association query at a wirelessclient device causes the wireless client device to transmit a responseto the association query.

When a wireless client device does not immediately associate using anidentified designated MAC address, the designated MAC address mayoptionally be released for use by other wireless client devices. Forexample, in one embodiment, a method of this aspect further comprisesmonitoring for an association request including the designated MACaddress for a predetermined time period; determining that no associationrequest including the designated MAC address is received during thepredetermined time period; and identifying the designated MAC address asavailable for use by another wireless client device.

Optionally, methods of this aspect may require additional authenticationbefore network services are available at a wireless client device. Inone embodiment, a method of this aspect further comprises facilitatingauthentication of the wireless client device after transmitting theassociation response. Additionally or alternatively, a method of thisaspect further comprises determining that the wireless client device hasnot successfully authenticated within a predetermined time period aftertransmitting the association response; and updating the associationtable to remove the entry for the wireless client device. Additionallyor alternatively, a method of this aspect comprises transmitting anauthentication query, such as where receiving the authentication at thewireless client device causes the wireless client device to transmit aresponse to the authentication query; monitoring for an authenticationresponse to the authentication query for a predetermined time period;determining that no authentication response is received during thepredetermined time period; and updating the association table to removethe entry for the wireless client device. Optionally, the authenticationquery and the response to the authentication query include elements ofan IEEE 802.1X authentication process. Optionally, the authenticationquery and the response to the authentication query include elements ofan IEEE 802.11i authentication process.

Methods of this aspect are optionally performed by wireless clientdevices. In specific embodiments, wireless client devices are configuredto request a designated MAC address prior to attempting association witha network device, such as an access point, for example an access pointcompliant with an IEEE 802.11 standard. In a specific embodiment, amethod of this aspect comprises transmitting, by a wireless clientdevice, a request for a media access control (MAC) address; receiving aresponse to the request, such as a response that is related to a networkdevice and that includes a designated MAC address; transmitting anassociation request, such as an association request that includes thedesignated MAC address; and receiving an association response that isrelated to the network device and that includes an associationidentifier. In various embodiments, a wireless client device may includesoftware features, specialized applications, or operating systemfeatures that make use of and/or recognize designated MAC addresses andemploy them as described herein. Optionally, security settings on anetwork may activate software features, specialized applications, oroperating system features that employ the methods described herein forusing designated MAC addresses.

As the identification and communication of the designated MAC addressmay occur prior to association, pre-association data exchanges may berequired. For example, in one embodiment, the MAC address requestincludes a Class 1 management frame, an action frame, an authenticationframe, or a probe request frame. In one embodiment, the response to theMAC address request includes a Class 1 management frame, an actionframe, an authentication frame, or a probe response frame.

In embodiments, the designated MAC address is identified by the networkdevice. Optionally, receiving the request at the network device causesthe network device to identify the designated MAC address. Optionally,the request for a MAC address includes an identifier corresponding tothe network device, such as a BSSID or network device MAC address.Optionally, receiving the association request at the network devicecauses the network device to confirm that the designated MAC addressincluded in the association request is authorized for use by thewireless client device. Optionally, receiving the association request atthe network device causes the network device to update an associationtable with an entry for the wireless client device, and wherein theentry includes the designated MAC address.

In embodiments where a network device advertises that it is providing orrequiring the use of designated MAC addresses, a wireless client devicemay be configured to detect such an advertisement and then request thedesignated MAC address prior to association. For example, in oneembodiment, a method of this aspect further comprises receiving anindicator of an availability of designated MAC addresses. Optionally,receiving the indicator includes receiving a beacon frame or a proberesponse frame, and wherein the beacon frame or probe response frameincludes the indicator. Optionally, a service set identifier (SSID) ofthe beacon frame or probe response frame includes the indicator.Optionally, a vendor specific element of the beacon frame or proberesponse frame includes the indicator.

In various embodiments, association table denial of service attacks areminimized by the network device by requiring additional data exchangewith a wireless client device before an entry in the association tablefor the wireless client device is made or in order to maintain it.Optionally, a method of this aspect further comprises receiving anassociation query that includes the designated MAC address; andtransmitting a response to the association query.

In various embodiments, additional authentication is required by anetwork device, such as authentication beyond that which takes place aspart of an association process. For example, authentication may berequired such as an IEEE 802.1X authentication. In one embodiment, amethod of this aspect further comprises transmitting an authenticationquery; monitoring for an authentication response to the authenticationquery for a predetermined time period; determining that anauthentication response is not received during the predetermined timeperiod; and updating the association table to remove the entry for thewireless client device. Optionally, receiving the authentication at thewireless client device causes the wireless client device to transmit aresponse to the authentication query. Optionally, receiving the responseto the authentication query at the network device causes the networkdevice to update an association table with an entry for the wirelessclient device, and wherein the entry includes the designated MACaddress. Optionally, the authentication query and the response to theauthentication query include elements of an IEEE 802.1X authenticationprocess or an IEEE 802.11i authentication process.

In embodiments, a network device may function to prevent or limitassociation table denial of service attacks. As described herein, anassociation table denial of service attack may occur when amalfunctioning or malicious device repeatedly associates with a networkdevice, such as a wireless access point, using different MAC addresses.For each association, an entry in an association table may be createdthat identifies the MAC address. As will be understood by the skilledartisan, an association table on a network device has a finite size,such as a size of 256. If 256 entries are present in the associationtable, additional wireless client devices may not be able to associatewith the network device. Association table entries may expire after afixed amount of time, but it is possible for a malfunctioning ormalicious device to fill up an association table in a shorter amount oftime than the expiry time. Additionally, if a malfunctioning ormalicious device is continuing to transmit repeated association requestswith different MAC addresses, new entries will be created as old entriesexpire, and the problem will persist.

Therefore, network devices may require an associated device to exchangeadditional data with the network device shortly after association inorder to maintain or create an association table entry. Alternatively oradditionally, a network device may track characteristics of a clientdevice that is transmitting multiple probe or association requests usingdifferent MAC addresses and may refuse or fail to acknowledge requeststhat are identified as being associated with that client device. Inthese ways, the risk of the association table filling up with erroneousor unused entries is minimized, as devices that exchange data with thenetwork device and/or do not transmit repeated association requests canbe considered to be properly associated and making use of theassociation table entry.

In a specific embodiment, a method of this aspect comprises receiving,at a network device, an association request, such as an associationrequest that is related to a wireless client device; transmitting anassociation response, such as an association response that includes anassociation identifier for the wireless client device; updating anassociation table with an entry for the wireless client device;transmitting an association query; monitoring for a response to theassociation query for a predetermined time period after transmitting theassociation response; determining that a response to the associationquery is not received during the predetermined time period; and updatingthe association table to remove the entry for the wireless clientdevice. Optionally, receiving the association query at a wireless clientdevice causes the wireless client device to transmit a response to theassociation query 22. Optionally, the network device is a wirelessaccess point compliant with an IEEE 802.11 standard. Optionally, thenetwork device is a network controller.

In another specific embodiment, a method of this aspect comprisesreceiving, at a network device, an association request, such as anassociation request that is related to a wireless client device;transmitting an association response, such as an association responsethat includes an association identifier for the wireless client device;transmitting an association query; monitoring for a response to theassociation query for a predetermined time period after transmitting theassociation response; and determining that a response to the associationquery is not received during the predetermined time period. Optionally,receiving the association query at a wireless client device causes thewireless client device to transmit a response to the association query.

In another specific embodiment, a method of this aspect comprisesreceiving, at a network device, an association request, such as anassociation request that is related to a wireless client device;transmitting an association response, such as an association responsethat includes an association identifier for the wireless client device;transmitting an association query; monitoring for a response to theassociation query for a predetermined time period after transmitting theassociation response; determining that a response to the associationquery is received during the predetermined time period; and updating anassociation table with an entry for the wireless client device.Optionally, receiving the association query at a wireless client devicecauses the wireless client device to transmit a response to theassociation query.

Various association queries are useful with methods of this aspect. Inembodiments, useful association queries are data messages that require aresponse, such as a reply, acknowledgment or other message that is sentin response to an association query. For example, in one embodiment, theassociation query includes a null data packet. Optionally, the responseto the association query includes an acknowledgement packet. Optionally,the association query includes a plurality of null data packets.Optionally, the response to the association query includes a pluralityof acknowledgement packets. In another embodiment, the association queryincludes an Internet Control Message Protocol echo request message, alsoknown as a ping message. Optionally, the response to the associationquery includes an Internet Control Message Protocol echo reply message,also known as a ping response. Optionally, the association queryincludes an identification request message, such as a request for anidentifier. Optionally, the response to the association query includes awireless client identifier. In another embodiment, the association queryincludes a dynamic host configuration protocol (DHCP) offer message.Optionally, the response to the association query includes a DHCPrequest message. Other embodiments are possible.

In some embodiments, the association query is a multi-component query.For example, the association query may include a series of sub-queriesthat are transmitted during a specified time period, such as starting at10 ms after an initial probe message and/or probe response message andoccurring every 5 ms for 5 separate sub-queries. In this way, a clientdevice that may initially request or respond but that later stopsresponding before the end of the series of sub-queries can have itsassociation table entry withheld or deleted. For example, in oneembodiment, determining that a response to the association query is notreceived during the predetermined time period includes determining thatonly an incomplete response to the association query is received duringthe predetermined time period.

Optionally, authentication steps may also be utilized as the associationquery and response to the association query. For example, in oneembodiment, the association query includes a request for authenticationand the response to the association query includes an authenticationcredential. Optionally, determining that a response to the associationquery is not received during the predetermined time period includesdetermining that the wireless client device has not successfullyauthenticated.

In some embodiments, authentication may be a separate process beyond theassociation query and response. Optionally, if initial associationcompletes but authentication does not complete successfully, anassociation table entry may be withheld or deleted and/or the clientdevice may be de-associated. In one embodiment, a method of this aspectfurther comprises facilitating authentication of the wireless clientdevice after transmitting new association response. Optionally, theassociation query and the response to the association query includeelements of an IEEE 802.1X authentication process.

In various embodiments, messages exchanged between a network device anda wireless client device identify a MAC address, such as a source MACaddress and a destination MAC address. The skilled artisan willappreciate that, typically, a source MAC address corresponds to the MACaddress of the device transmitting a message and a destination MACaddress corresponds to the MAC address of the intended device recipientof the message. One embodiment further comprises identifying a MACaddress included in the association request as different from a hardwareMAC address corresponding to the wireless client device. Alternativelyor additionally, one embodiment further comprises identifying a mediaaccess control (MAC) address included in the association request as arandomly assigned MAC address. Alternatively or additionally, oneembodiment further comprises identifying a media access control (MAC)address included in the association request as a randomly assigned MACaddress. Alternatively or additionally, one embodiment further comprisesidentifying a media access control (MAC) address included in theassociation request as a locally administered MAC address.

In some embodiments, wireless client devices that repeatedly transmitassociation requests may be blacklisted or have their associationrequests discarded. This may be difficult, however, if a wireless clientdevice is changing the MAC address for the multiple associationrequests. Embodiments described herein may make use of characteristicsof the wireless client device in order to determine that a singlewireless client device is responsible for repeated association requestseven though the association requests use different MAC addresses. Asdescribed above, useful characteristics include, but are not limited toa true or hardware MAC address of the wireless client device, a trackingcookie present on the wireless client device, a device identifiercorresponding to the wireless client device, a device profilecorresponding to the wireless client device, authentication credentialscorresponding to a user of the wireless client device, softwarecredentials corresponding to a software component present on thewireless client device, a token corresponding to the wireless clientdevice, a token corresponding to a user of the wireless client device, awireless signature characterizing the wireless transmission/reception orbroadcast characteristics of the wireless client device, a softwareprofile of the wireless client device, a hardware profile of thewireless client device, an actual or predicted location of the wirelessclient device, and the like.

In a specific embodiment, a method of this aspect further comprisesidentifying a plurality of association requests related to or identifiedas originating from a single wireless client device, such as where eachof the plurality of association requests include different media accesscontrol (MAC) addresses; and discarding additional association requestsrelated to or identified as originating from the single wireless clientdevice. Optionally, identifying includes identifying a characteristicrelated to the plurality of association requests, such as acharacteristic that facilitates determining that the plurality ofassociation requests originate from the single wireless client device.Optionally, identifying includes identifying a wireless signaturerelated to the plurality of association requests, such as a wirelesssignature that facilitates determining that the plurality of associationrequests originate from the single wireless client device. Optionally,identifying includes using location information related to the pluralityof association requests to facilitate determining that the plurality ofassociation requests originate from the single wireless client device.

In some configurations, a wireless client device that associates with anetwork device may enter a sleep period during which no data messagesare anticipated to be transmitted by the wireless client device. If anetwork device receives a data message addressed to a sleeping wirelessclient device, the network device may cache the data message for laterdelivery or may drop the data message. If a wireless client device is ina sleep period, transmitting an association query or a response to anassociation query may not be possible or may not result in a responsemessage. Optionally, the predetermined time period corresponds to awake-up period for the wireless client device. Optionally, thepredetermined time period may be different from some or all of theclient devices in communication and/or associated with the networkdevice. As used herein, a wake-up period corresponds to a time periodafter which a sleeping wireless client device is required to awaken andrespond to certain types of messages. If a wireless client device doesnot respond to an association query at the conclusion of thepredetermined period, its entry in an association table may be deleted.In this way, sleeping devices will not have their association tableentries inadvertently deleted.

For some embodiments, however, a wireless client that enters a sleepperiod immediately after association with a network device may have itsassociation table entry deleted, such as when the wireless client deviceenters a sleep period before transmitting some data to the networkdevice, such as network authentication data (e.g., 802.1X data), or arequest for a dynamic internet protocol (IP) address using DHCP. Forexample, in one embodiment, a method of this aspect may further comprisedetermining that the wireless client device has entered a sleep periodbefore a response to an association is received. Optionally, determiningthat a response to the association query is not received includesdetermining that the wireless client device has entered a sleep state.

In embodiments, sending association queries and receiving responses tothe association queries may take time and/or use wireless capacity, soit may be desirable to limit the amount of association queries andresponses transmitted. In one embodiment, transmission or associationqueries may only occur if the entries in the association table occupy aportion of the association table beyond a specified threshold. Forexample, in one embodiment, this method of deleting association tableentries may be set to begin only when a threshold of half of the maximumsize of the association table is filled with association entries. Inthis way, a network device can operate as normal for a considerableportion of time and only require responses to association queries fornew wireless client devices if the association table entries go beyondthe threshold number. For example, in one embodiment, a method of thisaspect further comprises identifying a number of entries in theassociation table; and comparing the number of entries in theassociation table with a threshold value, such that transmitting theassociation query and monitoring for the response to the associationquery are performed when the number of entries is larger than thethreshold value.

In other aspects, systems are provided, such as systems for performingthe methods described herein. In exemplary embodiments, a system of thisaspect comprises one or more processors, and a non-transitory computerreadable storage medium communicatively coupled or otherwise positionedin data communication with the one or more processors. In embodiments,the non-transitory computer readable storage medium includesinstructions that, when executed by the one or more hardware processors,cause the one or more hardware processors to perform one or more of themethods described herein.

For example, in a specific embodiment, a system of this aspect comprisesone or more processors, and a non-transitory computer readable storagemedium coupled with the one or more processors and includinginstructions that, when executed by the one or more processors, causethe one or more processors to perform operations including various stepsof the method embodiments described above.

In other aspects, computer program products are provided, such ascomputer program products configured to achieve methods describedherein. In exemplary embodiments, a computer program product of thisaspect is a non-transitory computer readable storage medium comprisinginstructions that, when executed by one or more hardware processors,cause the one or more hardware processors to perform one or more of themethods described herein.

For example, in a specific embodiment, a computer program product ofthis aspect comprises a non-transitory computer readable storage mediumcomprising instructions that, when executed by one or more processors,cause the one or more processors to perform operations including varioussteps of the method embodiments described above.

The terms and expressions which have been employed are used as terms ofdescription and not of limitation, and there is no intention in the useof such terms and expressions of excluding any equivalents of thefeatures shown and described or portions thereof, but it is recognizedthat various modifications are possible within the scope of theinvention claimed. Thus, it should be understood that although thepresent invention has been specifically disclosed by embodiments andoptional features, modification and variation of the concepts hereindisclosed may be resorted to by those skilled in the art, and that suchmodifications and variations are considered to be within the scope ofthis invention as defined by the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described indetail below with reference to the following drawing figures:

FIG. 1 illustrates a network configuration in accordance with someembodiments.

FIG. 2 illustrates a network configuration in accordance with someembodiments.

FIG. 3 illustrates a network configuration in accordance with someembodiments.

FIG. 4 illustrates a network configuration in accordance with someembodiments.

FIG. 5 illustrates an overview of the exchange of messages betweendevices during a wireless association process in accordance with someembodiments.

FIG. 6 illustrates an overview of the exchange of messages betweendevices during a wireless association process in accordance with someembodiments.

FIG. 7A and FIG. 7B illustrate overviews of the exchange of messagesbetween devices during a wireless association process in accordance withsome embodiments.

FIG. 8 illustrates an overview of a wireless denial of service attack inaccordance with some embodiments.

FIG. 9 illustrates an overview of the exchange of messages betweendevices during a wireless association process in accordance with someembodiments.

FIG. 10 is a block diagram illustrating an example of a wireless clientdevice in accordance with some embodiments.

FIG. 11 is a block diagram illustrating an example of an access point inaccordance with some embodiments.

FIG. 12 is a block diagram illustrating an example of a server inaccordance with some embodiments.

DETAILED DESCRIPTION

The ensuing description provides exemplary embodiments only, and is notintended to limit the scope, applicability, or configuration of thedisclosure. Rather, the ensuing description of the exemplary embodimentswill provide those skilled in the art with an enabling description forimplementing an exemplary embodiment. It should be understood thatvarious changes may be made in the function and arrangement of elementswithout departing from the spirit and scope of the invention as setforth in the appended claims.

Specific details are given in the following description to provide athorough understanding of the embodiments. However, it will beunderstood by one of ordinary skill in the art that the embodiments maybe practiced without these specific details. For example, circuits,systems, networks, processes, and other components may be shown ascomponents in block diagram form in order not to obscure the embodimentsin unnecessary detail. In other instances, well-known circuits,processes, algorithms, structures, and techniques may be shown withoutunnecessary detail in order to avoid obscuring the embodiments.

Also, it is noted that individual embodiments may be described as aprocess which is depicted as a flowchart, a flow diagram, a data flowdiagram, a structure diagram, or a block diagram. Although a flowchartmay describe the operations as a sequential process, many of theoperations can be performed in parallel or concurrently. In addition,the order of the operations may be re-arranged. A process is terminatedwhen its operations are completed, but could have additional steps notincluded in a figure. A process may correspond to a method, a function,a procedure, a subroutine, a subprogram, etc. When a process correspondsto a function, its termination can correspond to a return of thefunction to the calling function or the main function.

The term “machine-readable storage medium” or “computer-readable storagemedium” includes, but is not limited to, portable or non-portablestorage devices, optical storage devices, and various other mediumscapable of storing, containing, or carrying instruction(s) and/or data.A machine-readable medium may include a non-transitory medium in whichdata can be stored and that does not include carrier waves and/ortransitory electronic signals propagating wirelessly or over wiredconnections. Examples of a non-transitory medium may include, but arenot limited to, a magnetic disk or tape, optical storage media such ascompact disk (CD) or digital versatile disk (DVD), flash memory, memoryor memory devices. A computer-program product may include code and/ormachine-executable instructions that may represent a procedure, afunction, a subprogram, a program, a routine, a subroutine, a module, analgorithm, a software package, a class, or any combination ofinstructions, data structures, or program statements. A code segment maybe coupled to another code segment or a hardware circuit by passingand/or receiving information, data, arguments, parameters, or memorycontents. Information, arguments, parameters, data, etc. may be passed,forwarded, or transmitted via any suitable means including memorysharing, message passing, token passing, network transmission, etc.

Furthermore, embodiments may be implemented by hardware, software,firmware, middleware, microcode, hardware description languages, or anycombination thereof. When implemented in software, firmware, middlewareor microcode, the program code or code segments to perform the necessarytasks (e.g., a computer-program product) may be stored in amachine-readable medium. A processor(s) may perform the necessary tasks.

FIG. 1 illustrates one embodiment of a network configuration 100 thatmay be implemented for a multi-user organization, such as a business,educational institution, governmental entity, or any other organizationhaving multiple users and possibly multiple physical or geographicalsites. The network configuration 100 may include a main office 102 incommunication with a network 120. The network configuration 100 may alsoinclude one or more remote sites 132, 142, also in communication withthe network 120.

The main office 102 may include a primary network, possibly also calleda corporate network, enterprise network, or a home network. The mainoffice 102 network may be a private network. A private network is anetwork that may include security and access controls, such that onlyauthorized users may access the private network. Authorized users mayinclude, for example, employees of a company located in the main office102.

In the illustrated embodiment, the main office 102 includes a controller104 in communication with the network 120. The controller 104 mayprovide communication with the network 120 for the main office 102,though it may not be the only point of communication with the network120 for the main office 102. A single controller 104 is illustrated,though the main office may include multiple controllers and/or multiplecommunication points with network 120. In some embodiments, thecontroller 104 communicates with the network 120 through a router (notillustrated). In other embodiments, the controller 104 functions as arouter for the devices in the main office 102.

A controller 104 may be any device that is operable to configure andmanage network devices, such as the main office 102, and may also managenetwork devices at the remote sites 132, 142. The controller 104 may beoperable to configure and/or manage switches, routers, access points,and/or client devices connected to a network. The controller 104 mayitself be, or provide the functionality of, an access point.

The controller 104 may be in communication with one or more switches 108and/or wireless access points 106 a and 106 b. Switch 108 and wirelessaccess points 106 a-106 b provide network connectivity to various clientdevices 110 a, 110 b, 110 c, 110 d, 110 e, 110 f, 110 g, and 110 h.Using a connection to switch 108 or access point 106 a-106 b, a clientdevice 110 a-110 h is able to access network resources, including otherdevices on the network and the network 120.

Client devices 110 a-110 h include hardware devices that have processingcircuitry running at least one process adapted to control the flow oftraffic to and/or from the device, such as between the device andanother device on a network, such as another client device or networkinfrastructure devices. Client devices may also include user input andoutput interfaces and communication interfaces, such as a radio forwireless communication and/or a physical connector for wiredcommunication. Wireless client devices typically include a wirelessradio compliant with a wireless networking standard, such as an IEEE802.11 standard and are optionally adapted to associate with a wirelessnetwork infrastructure device, such as an access point. Examples ofclient devices include, but are not limited to: desktop computers,laptop computers, servers, web servers, authentication servers,authentication-authorization-accounting (AAA) servers, Domain NameSystem (DNS) servers, Dynamic Host Configuration Protocol (DHCP)servers, Internet Protocol (IP) servers, Virtual Private Network (VPN)servers, network policy servers, mainframes, tablet computers, netbookcomputers, televisions and similar monitors, content receivers, set-topboxes, personal digital assistants (PDAs), mobile phones, smart phones,smart terminals, dumb terminals, virtual terminals, video game consoles,printers, and the like.

Within the main office 102, a switch 108 is included as one example of apoint of access to the network for wired client devices 110 g and 110 h.Client devices 110 g and 110 h may connect to the switch 108 and throughthe switch 108 may be able to access other devices within the networkconfiguration 100. The client devices 110 g and 110 h may also be ableto access the network 120, through the switch 108. The client devices110 g and 110 h may communicate with the switch 108 over a wiredconnection 112. In the illustrated example, the switch 108 communicateswith the controller 104 over a wired connection 112, though thisconnection may also be wireless.

Wireless access points 106 a and 106 b are included as another exampleof a point of access to the network for client devices 110 a-110 f. Anaccess point 106 a-106 b is a combination of hardware, software, and/orfirmware that is configured to provide wireless network connectivity towireless client devices 110 a-110 f. In the illustrated embodiment, theaccess points 106 a-106 b can be managed and configured by thecontroller 104. The access points 106 a-106 b communicate with thecontroller 104 over either a wired connection 112 or a wirelessconnection 114.

Client devices within a network (e.g. wireless local area networks, or“WLANs”) communicate with access points in order to obtain access to oneor more network resources. An access point also referred to herein as an“AP”, may include a digital device that operates as a gateway for aclient device to establish a connection (e.g., a communicative coupling)with one or more networks (e.g., the Internet, an intranet, a local areanetwork, etc.). For example, an access point may be implemented as awireless access point (WAP), which is configured to communicatewirelessly with one or more client devices as well as communicate withother network devices associated with the one or more networks, such asa controller, router, or switch, for example, through a wired orwireless connection.

The network configuration 100 may include one or more remote sites 132,142. A remote site 132 may be located in a different physical orgeographical location from the main office 102. In some cases, theremote site 132 may be in the same geographical location, or possiblythe same building, as the main office, 102, but may lack a directconnection to the network located within the main office 102, relyinginstead on a connection over a different network 120. A remote site 132such as the one illustrated may be, for example, a satellite office. Theremote site 132 may include a gateway device 134 for communicating withthe network 120. A gateway device 134 may be a router, adigital-to-analog modem, a cable modem, a Digital Subscriber Line (DSL)modem, or some other network device configured to communicate with thenetwork 120. The remote site 132 may also include a router, switch 138and/or access point 136 in communication with the gateway 134 overeither wired or wireless connections. The router, switch 138 and accesspoint 136 provide connectivity to the network for various client devices140 a, 140 b, 140 c, and 140 d.

In various embodiments, the remote site 132 is in direct communicationwith main office 102, such that client devices 140 a-140 d at the remotesite 132 access the network resources at the main office 102 as if theseclients 140 a-140 d were located at the main office 102. In suchembodiments, the remote site 132 is managed by the controller 104 at themain office, and the controller 104 provides the necessary connectivity,security, and accessibility that enable communication between the remotesite 132 and the main office 102. Once connected to the main office 102,the remote site 132 may function as a part of a private network providedby the main office 102.

In various embodiments, the network configuration 100 may include one ormore smaller remote sites 142, comprising only a gateway device 144 forcommunicating with the network 120 and a wireless access point 146, bywhich various client devices 150 a and 150 b access the network 120.Such a remote site 142 may represent, for example, an individualemployee's home or a temporary remote office. The remote site 142 mayalso be in direct communication with the main office 102, such that theclient devices 150 a and 150 b at remote site 142 access networkresources at the main office 102 as if client devices 150 a and 150 bwere located at the main office 102. The remote site 142 may be managedby the controller 104 at the main office 102 to make this transparencypossible. Once connected to the main office 102, the remote site 142 mayfunction as a part of a private network provided by the main office 102.

The network 120 may be a public network, such as the Internet. A publicnetwork is a network that may be shared by an number of entities,including the illustrated network configuration 100. A public networkmay have unrestricted access, such that any user may connect to it. Thenetwork 120 may include any number of intermediate network devices, suchas switches, routers, gateways, servers, and/or controllers, that arenot directly illustrated as part of the network configuration 100 butthat facilitate communication between the various parts of the networkconfiguration 100, and between the network configuration 100 and othernetwork-connected entities. The network 120 may include various contentservers 160 a and 160 b. Content servers 160 a and 160 b may includevarious providers of multimedia downloadable and/or streaming content,including audio, video, graphical, and/or text content, or anycombination thereof. Examples of content servers 160 a and 160 binclude, for example, web servers, streaming radio and video providers,and cable and satellite television providers. The client devices 110a-110 h, 140 a-140 d, and 150 a-150 b may request and access themultimedia content provided by the content servers 160 a and 160 b.

FIG. 2 illustrates an embodiment of a network configuration 200 thatincludes a cloud-based management service 222. The network configuration200 may be implemented for a multi-user organization. The networkconfiguration 200 includes a main office 202 in communication with anetwork 220, and may also include one or more remote sites 232, 242,also in communication with the network 220. In the illustratedembodiment, the main office 202 includes a gateway device 204, such as arouter, for communicating with the network 220. A single gateway device204 is illustrated, though the main office 202 may include multiplegateway devices and/or multiple communication points with the network220.

The gateway device 204 may be in communication with one or more switches208 and/or wireless access points 206 a and 206 b. Switch 208 and accesspoints 206 a and 206 b provide network connectivity to various clientdevices 210 a, 210 b, 210 c, 210 d, 210 e, 210 f, 210 g, and 210 h.Using a connection to switch 208 or access points 206 a, 206 b, a clientdevice 210 a-210 h is able to access network resources, including otherdevices on the network and the network 220.

A switch 208 is included as an example of a point of access to thenetwork for client devices 210 g-210 h. Client devices 210 g-210 h maycommunicate with the switch 208 over a wired connection 212. Wirelessaccess points 206 a-206 b are included as another example of a point ofaccess to the network for client devices 210 a-210 f. Client devices 210a-210 f may communicate with the access points 206 a-210 b over wirelessconnections 214. The access points 206 a-b may themselves communicatewith the gateway device 204 over either wired connections 212 orwireless connections 214.

In the embodiment illustrated, the network configuration 200 includes acloud-based management service 222. The management service 222 mayinclude various software and software processes for configuring and/ormanaging network devices at the main office 202. Management tasks mayinclude, for example, access, authentication, security, hardwaremanagement, configuration and set-up, and/or internal and/or externalcommunication. The management service 222 may be running on a serverlocal to the main office 202, or a server located remotely from the mainoffice 202, or may be distributed across any number of local and/orremote servers. In embodiments where the management service 222 islocated remote to the main office 202, the management service 222 mayaccess the main office 202 over the network 220 or by way of gatewaydevice 204.

The network configuration 200 may include one or more remote sites 232,242. A remote site 232 may include a gateway device 234 forcommunicating with the network 220. The remote site 232 may also includea router, switch 238 and/or access point 236 in communication with thegateway device 234 over either wired or wireless connections. Therouter, switch 238 and access point 236 provide connectivity to thenetwork 220 for various client devices 240 a, 240 b, 240 c, and 240 d.

In various embodiments, the remote site 232 may be configured and/ormanaged by, the management service 222, such that client devices 240a-240 d at the remote site 232 access the network resources at the mainoffice 202 as if these clients 240 a-240 d were located at the mainoffice 202. The management service 222 provides all, or parts of, thenecessary connectivity, security, and accessibility that enablecommunication between the remote site 232 and the main office 202.

In various embodiments, the network configuration 200 may also includeone or more smaller remote sites 242, comprising only a gateway device244 for communicating with the network 220 and a wireless access point246, by which various client devices 250 a and 250 b access the network220. The remote site 242 may also be configured and/or managed by themanagement service 222, such that the client devices 250 a-250 b at theremote site 242 access network resources at the main office 202 as ifthese client devices 250 a-250 b were located at the main office 202.The management service's 222 control over the remote site 242 makes thistransparency possible.

The network 220 may be a public network, such as the Internet. Thenetwork 220 may include various content servers 260 a and 260 b. Theclient devices 210 a-210 h, 240 a-240 d, 250 a-250 b may request andaccess data and content provided by the content servers 260 a-260 b overtheir connection to the network 220.

FIG. 3 illustrates an embodiment of a network configuration 300. Asillustrated, controller 302 provides connectivity between network 320and other network devices within network configuration 300, althoughconnectivity with network 320 may be optionally provided by way ofanother device, such as network device 304 or one or more gateways,routers, switches, hubs, modems, etc. Controller 302 may includefunctionality of a router, switch, gateway, access point, etc., in orderto provide network connectivity with network 320 and between otherdevices within network configuration 300. Controller 302 may optionallyinclude a wireless access point. Controller 302 may also function as acentral management point for other devices within network configuration300, such as wired and/or wireless network devices, and may provideaddressing services, configuration control, routing services, and thelike.

As illustrated, network devices 304 and 306 are connected to controller302 by way of direct network connections, though embodiments arecontemplated where one or more intermediate devices and/or networks arepositioned between network devices 304, 306 and controller 302 and/orwhere network devices 304, 306 are wirelessly connected to controller302. In turn, network device 304 provides network access between networkdevice 308 and controller 302. Network devices 304, 306, and 308 mayfunction as switches, routers, hubs, gateways, access points, etc., andmay also provide network connectivity to one or more wired clientdevices (not shown).

Wireless access point 310 also connects to controller 302 by a directnetwork connection and may provide wireless access to network servicesto one or more wireless client devices (not shown). Wireless accesspoint 310 may also provide wireless access between controller 302 andwireless access point 312, with wireless access point 312 optionallyfunctioning as a wireless range extender or wireless bridge andproviding wireless connectivity to other wireless client devices (notshown). Wireless access points 314, 316, and 318 are illustrated asrespectively connected to network devices 304, 306, and 308, and mayprovide network connectivity to one or more wireless client devices. Asillustrated, wireless access points 310, 312, 314, 316, and 318 aremanaged by controller 302, which provides configuration, addressing,routing, and other services to facilitate wireless access points 310,312, 314, 316, and 318 providing network connectivity to wireless clientdevices. Controller 302 may optionally provide additional services, suchas authentication services, to wired network devices, wired clientdevices, wireless access points, and wireless client devices of networkconfiguration 300.

FIG. 4 illustrates a network configuration 400, which may optionallyrepresent a subset of any of network configurations 100, 200, and/or300. For example, network 420 may represent any the remainder of any ofnetwork configurations 100, 200, and/or 300 that are not illustratedexplicitly in FIG. 4.

In FIG. 4, wireless access point 402 provides network connectivity toassociated wireless client devices 404 and 406. Wireless client device408, however, is illustrated as not associated with wireless accesspoint 402. Although wireless client device 408 is not associated withwireless access point 402, wireless client device 408 and wirelessaccess point 402 may still exchange data communications, such as sendingor receiving probe requests/responses, or for establishing a wirelessassociation or other purposes.

For example, wireless client device 408 may transmit probe requestframes, action frames, authentication frames, and other class 1 wirelessframes, such as class 1 control or management frames, which may bereceived and processed by wireless access point 402, even though clientdevice 408 is not associated with wireless access point 402. Similarly,wireless access point 402 may transmit beacon frames, probe responseframes, and other class 1 wireless frames, such as class 1 control ormanagement frames, which may be received and processed by wirelessclient device 408, even though client device 408 is not associated withwireless access point 402.

As will be understood by the skilled artisan, the data communicationsthat are exchanged between wireless client device 408 and wirelessaccess point 402 may reveal a media access control (MAC) address ofwireless client device 408. In embodiments, use of a MAC address ofwireless client device 408 ensures that data communications transmittedby wireless access point 402 for receipt by wireless client device 408will not be acted upon by another wireless client device that mayreceive the data communications.

Although wireless client device 408 may have a hardware (HW) MAC address412, also called a manufacturer assigned or true MAC address, wirelessclient device 408 may use another MAC address for these pre-associationdata communications, such as a random MAC address. For example, asillustrated, the hardware MAC 412 address of wireless client device 408is C8-85-50-66-70-CC, but the random MAC address communicated in theprobe request 425 is 7A-A1-E1-14-2B-B1. In response to the probe request425, the access point 402 transmits probe response 430, identifying asthe destination MAC address the source MAC address in probe request 425(in this example, 7A-A1-E1-14-2B-B1).

FIG. 5 illustrates an overview of the exchange of data messages betweenwireless client device 408 and access point 402 during a wirelessassociation process. Initially, access point 402 may transmit a beacon505. Beacon 505 includes the service set identifier (SSID)“Wireless-Network” and the basic service set identifier (BSSID) of theaccess point 402. As will be understood by the skilled artisan, theBSSID of the access point 402 may correspond to the wireless MAC addressof access point 402.

Wireless client device 408 transmits a probe request 510, which includesa source MAC address selected for wireless client device 408. Asdescribed previously, wireless client device 408 may optionally use analternative MAC address that is different from HW MAC address 412. Aswill be understood by the skilled artisan, probe request 510 may usestored information or information from beacon 505 and correspond to adirected probe request that identifies a wireless network by SSID.Alternatively, probe request 510 may be a broadcast probe that does notinclude an SSID (or may specify a null SSID), in which case all accesspoints that receive the probe request 510 may generate a probe response.As illustrated, probe request 510 includes the SSID “Wireless-Network”,which corresponds to the SSID in use by access point 402.

Access point 402 receives probe request 510 and transmits probe response515. The MAC address/BSSID 416 of access point 402 is identified inprobe response 515 as the source MAC address. Probe response 515 alsoincludes a destination MAC address that matches the source MAC addressincluded in probe request 510, namely the random MAC address transmittedby wireless client device 408. In this way, the HW MAC address 412 hasbeen masked from access point 402 during the process of transmitting andreceiving probe request 510 and probe response 515.

When wireless client device 408 is ready to associate with access point402, wireless client device 408 transmits an authentication request 520.As illustrated, authentication request 520 identifies the source MACaddress as the HW MAC address 412 of wireless client device 408. In someembodiments, however, wireless client device 408 may continue to use aMAC address other than its HW MAC address 412 for authentication withwireless access point 402. Authentication request 520 further includesBSSID 416 as the destination MAC address. The skilled artisan willappreciate that other information may be included in authenticationrequest 520, for example, as required by a wireless networking standard,such as an IEEE 802.11 standard.

After receiving authentication request 520, access point 402 may confirmor otherwise act upon the information included in authentication request520 and generate and transmit an authentication response 525. Asillustrated, authentication response 525 includes a source MAC addresscorresponding to BSSID 416 and a destination MAC address correspondingto the source MAC address included in authentication request 520,namely, in this example, HW MAC address 412. Again, the skilled artisanwill appreciate the information and process required for authenticationof wireless client device 408, the generation of authentication response525, and other information that may be included in authenticationresponse 525.

To continue the association process, with access point 402, wirelessclient device 408 transmits an association request 530. As illustrated,association request 530 identifies the source MAC address as the HW MACaddress 412 of wireless client device 408, and BSSID 416 as thedestination MAC address. Once again, the skilled artisan will appreciatethat other information that may be included in association request 530.

After receiving association request 530, access point 402 may confirm orotherwise act upon the information included in association request 530and generate and transmit an association response 535. As illustrated,association response 535 includes a source MAC address corresponding toBSSID 416 and a destination MAC address corresponding to the source MACaddress included in association request 530, namely, in this example, HWMAC address 412. Again, the skilled artisan will appreciate that otherinformation may be included in association response 535. For example,association response 535 further includes an association ID. Uponreceiving the association response 535 including the association ID, thewireless client device 408 may consider itself as associated with accesspoint 402.

In addition to transmitting association response 535, access point 402further updates an association table, at 540, with an entry for wirelessclient device 408, which may identify wireless client device 408 by theassociation ID, and HW MAC address, which was included in authenticationrequest 520 and association request 530 as the source MAC address ofthese messages. Although the updating of the association table is shownas occurring after association response 535 is transmitted, theassociation table may be updated before or simultaneous withtransmission of association response 535. After successful association,wireless client device 408 and access point 402 can exchange data 545with one another.

FIG. 6 illustrates an overview of the exchange of data messages betweenwireless client device 408 and access point 402 during a wirelessassociation process of another embodiment. As will be understood by theskilled artisan making reference to FIG. 5, beacon signals, proberequests, probe responses, authentication requests, and authenticationresponses may be exchanged between wireless client device 408 and accesspoint 402 before and during a wireless association process. So as not toobscure FIG. 6 with excessive detail, however, beacon signals, proberequests, probe responses, authentication requests, and authenticationresponses are not illustrated.

As illustrated, wireless client device 408 transmits a MAC addressrequest 605 that identifies a source MAC address and BSSID 416 as thedestination MAC address. For example the source MAC address included inMAC address request 605 may be a random and/or locally administered MACaddress. In some embodiments, however, the source MAC address is the HWMAC address 412 of wireless client device 408.

In response to receiving MAC address request 605, access point 402 mayidentify, at 610, a designated MAC address for use by wireless clientdevice 408. The designated MAC address may be included in MAC addressresponse 615 that is transmitted by access point 402 for receipt bywireless client device 408. Access point 402 may indicate that theidentified designated MAC address has been reserved for use by wirelessclient device 408, such as in a reservation table or other database orlist accessible by access point 402. For example, access point 402 maytrack wireless client device 408 using the source MAC address includedin MAC address request 605 or another identifier or characteristic ofwireless client device 408.

As illustrated, MAC address request 605 and MAC address response 615 aretransmitted prior to wireless association between wireless client device408 and access point 402. Accordingly, MAC address request 605 and MACaddress response 615 may be transmitted in or as class 1 managementframes, action frames, authentication frames, and/or probe request/proberesponse frames. Other embodiments are possible.

In one embodiment, MAC address request 605 may correspond to a proberequest that includes a random or locally managed MAC address as thesource MAC address. Optionally, this probe request may not have anyother indicators of the probe request being a request for a designatedMAC address. For example, the wireless client may send a standard proberequest and not one that specifically requests a designated MAC address.Whether or not a specific request for a designated MAC address is made,however, in this embodiment, access point 402 may treat the proberequest as a request for a designated MAC address request, and, inresponse, transmit a probe response that includes an identifieddesignated MAC address.

As illustrated, after receiving MAC address response 615, wirelessclient device 408 transmits an association request 620 that includes thedesignated MAC address as the source MAC address and BSSID 416 as thedestination MAC address. The skilled artisan will appreciate that otherinformation that may be included in association request 620.

If the wireless client device fails to use the designated MAC address inthe association request 620 or if association fails or is not completed,at 625 the designated MAC address is released or marked as unreserved,making the designated MAC address available for use by other wirelessclient devices.

After receiving association request 620, access point 402 may confirm orotherwise act upon the information included in association request 620and generate and transmit an association response 630. As illustrated,association response 630 includes a source MAC address corresponding toBSSID 416 and a destination MAC address corresponding to the designatedMAC address included as the source MAC address in association request620. Again, the skilled artisan will appreciate that other informationthat may be included in association response 630. For example,association response 630 further includes an association ID. Uponreceiving the association response 630 including the association ID, thewireless client device 408 may consider itself as associated with accesspoint 402.

In addition to transmitting association response 630, access point 402further updates an association table, at 635, with an entry for wirelessclient device 408, which may identify wireless client device 408 by theassociation ID, and/or designated MAC address. Although the updating ofthe association table is shown as occurring after association response630 is transmitted, the association table may be updated before orsimultaneous with transmission of association response 630. Theassociation table may be located on the access point 402, or on acontroller or other network device.

After successful association, wireless client device 408 and accesspoint 402 may be able to exchange data 655 with one another. In someembodiments, however, only certain data may be transmitted, such as datarequired for authenticating wireless client device 408. As illustratedin FIG. 6, access point 402 may transmit an authentication query 640 forreceipt by wireless client device 408. Following this, wireless clientdevice 408 may transmit a response to the authentication query, alsocalled an authentication reply 645, for receipt by wireless access point402. For example, authentication query 640 and authentication reply 645may correspond to data messages exchanged between wireless client device408 and wireless access point 402 during an IEEE 802.1X authenticationprocess. Optionally, authentication query 640 and authentication reply645 may correspond to data messages exchanged between wireless clientdevice 408 and wireless access point 402 during a wirelessauthentication process. In some embodiments, additional types of datamay be exchanged between wireless client device 408 and access point 402but, prior to an authentication process, access point 402 may not allowtransmission over the network of certain data or messages originatingfrom wireless client device 408 that have a destination addressdifferent from access point 402 and/or may not allow transmission towireless client device of certain data or messages received by accesspoint 402 from other devices over the network.

After successful authentication, data 655 may be exchanged betweenwireless client device 408 and access point 402. If authenticationremains incomplete, such as upon a timer elapsing or the wireless clientdevice 408 begins using a different MAC address from the designated MACaddress after authentication, the association table entry correspondingto wireless client device 408 may be deleted or removed from theassociation table, at 650. Alternatively or additionally, the designatedMAC address may be released for use by another wireless client device.

FIG. 7A and FIG. 7B illustrate overviews of the exchange of datamessages between wireless client device 408 and access point 402 duringa wireless association process of another embodiment. As will beunderstood by the skilled artisan making reference to FIG. 5, beaconsignals, probe requests, probe responses, authentication requests, andauthentication responses may be exchanged between wireless client device408 and access point 402 during a wireless association process. So asnot to obscure FIG. 7A and FIG. 7B with excessive detail, however,beacon signals, probe requests, probe responses, authenticationrequests, and authentication responses may not be illustrated.

As illustrated, in FIG. 7A, wireless client device 408 transmits anassociation request 705 that identities a source MAC address and BSSID416 as the destination MAC address. For example, the source MAC addressincluded in association request 705 may be a random and/or locallyadministered MAC address. In some embodiments, however, the source MACaddress is the HW MAC address 412 of wireless client device 408.

In response to receiving association request 705, access point 402 maytransmit an association response including an association ID. Uponreceiving the association response 630 including the association ID, thewireless client device 408 may consider itself as associated with accesspoint 402. Additionally, access point 402 may identify, at 715, adesignated MAC address for use by wireless client device 408. Thedesignated MAC address may be included in association response 710 thatis transmitted by access point 402 for receipt by wireless client device408 or may be included in a separate data message 720. Access point 402may identify designated MAC address as having been reserved for use bywireless client device 408, such as by an entry in a reservation tableor other database or list accessible by access point 402. For example,access point 402 may track wireless client device 408 using the sourceMAC address included in MAC address request 605 or another identifier orcharacteristic of wireless client device 408.

After the designated MAC address is communicated to wireless clientdevice 408, one or more disassociation messages are exchanged betweenwireless client device 408 and access point 402. For example, accesspoint 402 may transmit a deauthentication frame or a disassociationframe. Alternatively or additionally, if properly configured to do so,wireless client device 408 may transmit a deauthentication frame or adisassociation frame upon receipt of the designated MAC address. Forexample, then, the association corresponding to the association IDincluded in association response 710 is terminated.

As illustrated, in FIG. 7B, wireless client device 408 transmits anauthentication request 706 that identities a source MAC address andBSSID 416 as the destination MAC address. For example, the source MACaddress included in authentication request 706 may be a random and/orlocally administered MAC address. In some embodiments, however, thesource MAC address is the HW MAC address 412 of wireless client device408.

In response to receiving authentication request 706, access point 402may identify, at 715, a designated MAC address for use by wirelessclient device 408. The designated MAC address may be included inauthentication response 711 that is transmitted by access point 402.Access point 402 may identify designated MAC address as having beenreserved for use by wireless client device 408, such as by an entry in areservation table or other database or list accessible by access point402. For example, access point 402 may track wireless client device 408using the source MAC address included in MAC address request 605 oranother identifier or characteristic of wireless client device 408.

As illustrated in both FIG. 7A and FIG. 7B, An association request 730is transmitted by wireless client device 408 that includes thedesignated MAC address as the source address. Other information beyondthat illustrated may be included in the association request 730.

If association fails or is otherwise incomplete, at 735 the designatedMAC address is released or marked as unreserved, making the designatedMAC address available for use by other wireless client devices.

After receiving association request 730, access point 402 may confirm orotherwise act upon the information included in association request 730and generate and transmit an association response 740. As illustrated,association response 740 includes a source MAC address corresponding toBSSID 416 and a destination MAC address corresponding to the designatedMAC address included as the source MAC address in association request730. Again, the skilled artisan will appreciate that other informationthat may be included in association response 740. For example,association response 740 further includes a new association ID. Uponreceiving the association response 740 including the association ID, thewireless client device 408 may consider itself as associated with accesspoint 402. Upon receiving the association response 740 including theassociation ID, the wireless client device 408 may again consider itselfas associated with access point 402 but now will be associated withreference to the designated MAC address.

In addition to transmitting association response 740, access point 402further updates an association table, at 745, with an entry for wirelessclient device 408, which may identify wireless client device 408 by theassociation ID, and/or designated MAC address. Although the updating ofthe association table is shown as occurring after association response740 is transmitted, the association table may be updated before orsimultaneous with transmission of association response 740.

After successful association, wireless client device 408 and accesspoint 402 may be able to exchange data 765 with one another. In someembodiments, however, only certain data may be transmitted, such as datarequired for authenticating wireless client device 408. As illustratedin FIG. 7A and FIG. 7B, access point 402 may transmit an authenticationquery 750 for receipt by wireless client device 408. Following this,wireless client device 408 may transmit an authentication reply 755 forreceipt by wireless access point 402. For example, authentication query750 and authentication reply 755 may correspond to data messagesexchanged between wireless client device 408 and wireless access point402 during an IEEE 802.1X authentication process or wirelessauthentication process. Optionally, authentication query 750 andauthentication reply 755 may correspond to data messages exchangedbetween wireless client device 408 and wireless access point 402 duringa wireless authentication process.

After successful authentication, data 765 may be exchanged betweenwireless client device 408 and access point 402. If authenticationremains incomplete, such as upon a timer elapsing, the association tableentry corresponding to wireless client device 408 may be deleted orremoved from the association table, at 760. Additionally oralternatively, the designated MAC address may be released for use byanother wireless client device.

Allowing the use of random or locally administered MAC addresses maymake an access point vulnerable to a denial of service (DOS) typeattack. For example, a device may repeatedly associate with an accesspoint, creating multiple entries in an association table, with eachassociation using a distinct MAC address, and thereby occupy all entriesin an association table and prevent additional wireless client devicesfrom associating with the access point.

FIG. 8 provides an overview of a wireless DOS attack in which wirelessclient device 408 repeatedly associates with access point 402. Asillustrated, wireless client device 408 transmits an authenticationrequest 805 that includes a source MAC address, such as a source MACaddress different from the HW MAC address 412 of wireless client device408. In response, upon successful authentication (e.g., open systemsauthentication), access point 402 transmits authentication response 810.Wireless client device 408 then transmits an association request 815that includes a different source MAC address from that in the originalassociation request 805. Access point 402 then transmits an associationresponse 820 including an association ID and updates an associationtable, at 825, with an entry for the MAC address included as the sourceMAC address in authentication request 805 and association request 815.

To continue the DOS attack, wireless client device 408 transmits anauthentication request 830 that includes a source MAC address differentfrom the source MAC address included in authentication request 805 andassociation request 815. In response, upon successful authentication(e.g., open systems authentication), access point 402 transmitsauthentication response 835. Wireless client device 408 then transmitsan association request 840. Access point 402 then transmits anassociation response 845 including an association ID and updates anassociation table, at 850, with an entry for the MAC address included asthe source MAC address in authentication request 830 and associationrequest 840. This process may be repeated by wireless client device 408until the association table is full and cannot accept additionalentries.

Embodiments are contemplated herein for minimizing such a DOS attack byrequiring additional data exchange between a wireless client device andan access point for creation or maintaining of an association tableentry. FIG. 9 illustrates an overview of the exchange of data messagesbetween wireless client device 408 and access point 402 during awireless association process of an embodiment for preventing a DOSattack.

In FIG. 9, wireless client device 408 transmits an authenticationrequest 905, which may include a random and/or locally administered MACaddress. Optionally, authentication request may include HW MAC address412. The skilled artisan will understand additional information that maybe included in authentication request 905.

After receiving authentication request 905, access point 402 may confirmor otherwise act upon the information included in authentication request905 and generate and transmit an authentication response 910. Asillustrated, authentication response 910 includes a source MAC addresscorresponding to BSSID 416 and a destination MAC address correspondingto the source MAC address included in authentication request 905. Again,the skilled artisan will appreciate the information and process requiredfor authentication of wireless client device 408, the generation ofauthentication response 910, and other information that may be includedin authentication response 910.

To continue the association process, with access point 402, wirelessclient device 408 transmits an association request 915. As illustrated,association request 915 identifies the same source and destination MACaddresses included in authentication request 905. Once again, theskilled artisan will appreciate that other information that may beincluded in association request 915.

After receiving association request 915, access point 402 may confirm orotherwise act upon the information included in association request 915and generate and transmit an association response 920. As illustrated,association response 535 includes a source MAC address corresponding toBSSID 416 and a destination MAC address corresponding to the source MACaddress included in association request 915. Again, the skilled artisanwill appreciate that other information that may be included inassociation response 920. For example, association response 920 furtherincludes an association ID. Upon receiving the association response 920including the association ID, the wireless client device 408 mayconsider itself as associated with access point 402.

In addition to transmitting association response 920, access point 402further updates an association table, at 925, with an entry for wirelessclient device 408, which may identify wireless client device 408 by theassociation ID, and MAC address that was included as the source MACaddress in authentication request 905 and association request 915.Although the updating of the association table is shown as occurringafter association response 920 is transmitted, the association table maybe updated before or simultaneous with transmission of associationresponse 920. After successful association, wireless client device 408and access point 402 may be able to exchange data 960 with one another.

For purposes of preventing the association table from filling up witherroneous or abandoned entries, access point 402 may transmit anassociation query 930 for which an association reply 935 is required.For example, association query may include a series of one or more nulldata packets (NDPs), and association reply 935 may include one or moreacknowledgment (ACK) signals. If no or only an incomplete associationreply 935 is received, the entry for wireless client device 408 in theassociation table is deleted. In this way, association table entries areonly maintained for wireless client devices which are associated withthe access point for long enough to successfully reply to an associationquery.

Although illustrated as separate steps, 925 and 940 may be combined. Forexample, the association table entry may not be created until after asuccessful association reply 935 is received at access point 402. Inthis way, only devices which pass the association reply 935 requirementare given association table entries. Such a configuration minimizes theaddition and subsequent deletion of association table entries by onlycreating table entries if a suitable association reply 935 is receivedor never creating table entries for devices which do not generate asuitable association reply.

After successful association, wireless client device 408 and accesspoint 402 may be able to exchange data 960 with one another. In someembodiments, however, only certain data may be transmitted by accesspoint 402, such as data required for authenticating wireless clientdevice 408. For example, in some embodiments, prior to successfulauthentication, access point 402 may not transmit data or messagesreceived by it over the network that are addressed to wireless clientdevice other than data or messages used for the authentication process.As illustrated in FIG. 9, access point 402 may transmit anauthentication query 945 for receipt by wireless client device 408.Following this, wireless client device 408 may transmit anauthentication reply 950 for receipt by wireless access point 402. Forexample, authentication query 945 and authentication reply 950 maycorrespond to data messages exchanged between wireless client device 408and wireless access point 402 during an IEEE 802.1X or IEEE 802.11iauthentication process.

After successful authentication, data 960, including messages receivedover the network by access point 402 that are addressed to wirelessclient 408, may be exchanged between wireless client device 408 andaccess point 402. If authentication remains incomplete, such as upon atimer elapsing, the association table entry corresponding to wirelessclient device 408 may be deleted or removed from the association table,at 955.

Optionally, association query 930 is transmitted only when a number ofentries in the association table is equal to or larger than a thresholdvalue. For example, in some embodiments, if the number of entries islarger than a threshold value, the association query process is bypassedand the association table entry is maintained without requiring anassociation reply. Therefore, in some embodiments, access point 402 maydetermine a size of the association table and compare it to a thresholdand transmit the association query when the size of the associationtable is equal to and/or larger than the threshold.

Optionally, association query 930 is transmitted only when the sourceMAC address included in authentication request 905 and associationrequest 915 is identified as a random or locally administered MACaddress. For example, in some embodiments, if the source MAC addressincluded in authentication request 905 and association request 915 isidentified as a HW MAC address, a designated MAC address, or apreviously observed MAC address, the association query process isbypassed and the association table entry is maintained without requiringan association reply.

The process illustrated in FIG. 9 may optionally be combined with theassignment of designated MAC addresses described above and/orillustrated in FIGS. 6 and 7A and 7B.

FIG. 10 illustrates an example of a client device 1000, such as awireless client device that can connect to a wireless network, forexample by association with an access point. Client devices may also bereferred to herein as wireless devices, stations, and the like. Theclient device 1000 includes hardware elements that can be electricallycoupled via a bus 1018 (or may otherwise be in communication, asappropriate). In one embodiment, the bus 1018 can be used for theprocessor(s) 1002 to communicate between cores and/or with the memory1012. The hardware elements may include one or more processors 1002,including without limitation one or more general-purpose processorsand/or one or more special-purpose processors (such as digital signalprocessing chips, graphics acceleration processors, and/or the like);one or more input devices 1016; one or more output devices 1014; and oneor more wireless transceivers 1006. Optionally, input device 1016 caninclude numerous devices including, without limitation, a camera, amouse, a keyboard, a touch sensitive screen, a touch pad, a keypad,and/or the like. Optionally, output device 1014 can include numerousdevices including, but not limited to, a display, a printer and/or thelike. Client devices optionally include one or more network interfaces1020, such as for network communications over a wired medium, such as atwisted pair cable, a coaxial cable, a fiber optic cable or othernetwork communication cable. For example, network interface 1020 mayprovide for a wired network connection to an IEEE 802.3 compliantEthernet network.

The client device 1000 includes one or more wireless transceivers 1006connected to the bus 1018. The wireless transceiver 1006 may be operableto transmit and/or receive wireless signals (e.g., signal 1010) via oneor more antennas 1008. A wireless signal 1010 received by client device1000 may be transmitted via a wireless device compliant with a wirelesscommunications standard that the client device 1000 supports. A wirelesssignal 1010 transmitted by client device 1000 may be a wireless signalcompliant with a wireless communications standard that the client device1000 supports. For example, embodiments are contemplated where thewireless communications standard is one or more of IEEE 802.11,Bluetooth, Zigbee, UWB, wireless USB, Z-Wave and the like. In anexemplary embodiment, the wireless communications standard is an IEEE802.11 standard, such as 802.11n or 802.11ac. Wireless transceiver 1006may be configured to transmit and/or receive various radio frequency(RF) signals (e.g., signal 1010) via antenna 1008 from one or gateways,network devices, access points, other client devices, cellular networks,and/or the like. Client device 1000 may also be configured to decodeand/or decrypt various signals received.

The client device 1000 may further include (and/or be in communicationwith) one or more non-transitory machine-readable storage mediums orstorage devices (e.g., memory 1012), which can comprise, withoutlimitation, local and/or network accessible storage, and/or can include,without limitation, a disk drive, a drive array, an optical storagedevice, a solid-state storage device such as a random access memory(“RAM”) and/or a read-only memory (“ROM”), which can be programmable,flash-updateable and/or the like. Such storage devices may be configuredto implement any appropriate data storage, including without limitation,various file systems, database structures, and/or the like.

In various embodiments, functions may be stored as one or morecomputer-program products, such as instructions or code, in memory 1012,such as RAM, ROM, FLASH, or disc drive, and executed by processor(s)1002. The client device 1000 can also comprise software elements orfunctions (e.g., located within the memory 1012), including, forexample, an operating system, device drivers, executable libraries,and/or other code, such as one or more application programs, which maycomprise computer programs implementing various functions. Memory 1012may be a non-transitory machine-readable storage medium,processor-readable memory, and/or a computer-readable memory that storesthe one or more computer-program products configured to cause theprocessor(s) 1002 to perform various functions. In other embodiments,various functions described may be performed in hardware.

FIG. 11 illustrates an example of an access point 1100. The access point1100 may optionally include or otherwise function as a range extendingdevice, a router, a gateway, a modem, and/or any other device thatprovides network access among one or more computing devices and/ornetworks. For example, access point 1100 may include a router gatewaywith access point and router functionality, and may further include anEthernet switch and/or a modem. As another example, the access point1100 may include a range extender that may be used to improve signalrange and strength within a wireless network by taking an existingsignal from another access point and rebroadcasting the signal to createan expanded logical network. Optionally, access point 1100 may includeor otherwise function as a network controller for configuring and/ormanaging itself and/or other access points.

The access point 1100 includes hardware elements that can beelectrically coupled via a bus 1118 (or may otherwise be incommunication, as appropriate). In one embodiment, the bus 1118 can beused for the processor(s) 1102 to communicate between cores and/or withthe memory 1112. The hardware elements may include one or moreprocessors 1102, including without limitation one or moregeneral-purpose processors and/or one or more special-purpose processors(such as digital signal processing chips, graphics accelerationprocessors, and/or the like); one or more input devices 1116, which caninclude without limitation one or more buttons, a keyboard, a keypad, atouch sensitive screen, a touch pad, and/or the like; and one or moreoutput devices 1114, which can include, without limitation, a display,light or sound indicators, and/or the like.

The access point 1100 may include one or more wireless transceivers 1106connected to the bus 1118. The wireless transceiver 1106 may be operableto receive and transmit wireless signals (e.g., a wireless signal 1110)via an antenna 1108. The wireless transceiver 1106 may include atransceiver radio designed to transmit and receive signals in compliancewith a wireless communications standard. Exemplary wirelesscommunications standards include, but are not limited to, IEEE 802.11(also referred to herein as WiFi or Wi-Fi), Bluetooth, Zigbee, UWB,wireless USB and Z-Wave. In various embodiments, a wirelesscommunications standard specifies frequency bands, channels, data packetcharacteristics and other transmission characteristics necessary forinter device-communication. For example, wireless transceiver 1106 mayinclude a 2.4 GHz WiFi circuit or a 5 GHz WiFi circuit. Accordingly, theaccess point 1100 may include a single WiFi circuit for a WiFicommunications, and a single Bluetooth circuit for Bluetoothcommunications. In some embodiments, the access point 1100 may includemultiple wireless transceivers (not shown) for each availablecommunications standard. The antenna 1108 may include multiple bandantennas that can transmit and/or receive signals over differentfrequency bands.

The access point 1100 may further include a radio frequency (RF)circuit. In some embodiments, the wireless transceiver 1106 may beintegrated with or coupled to the RF circuit so that the RF circuitincludes the wireless transceiver 1106. In some embodiments, thewireless transceiver 1106 and the RF circuit are separate components.The RF circuit may include a RF amplifier that may amplify signalsreceived over antenna 1108. The RF circuit may also include a powercontroller that may be used to adjust signal amplification by the RFamplifier. The power controller may be implemented using hardware,firmware, software, or any combination thereof.

The wireless signal 1110 may be transmitted via a wireless communicationchannel. In some embodiments, the wireless communication channel may beany wireless communication channel established between two or moredevices, such as a wireless local area network (e.g., a WiFi network), aPersonal Access Network (e.g., between Bluetooth, Zigbee, UWB orwireless USB compatible devices), or a cellular network (e.g., a GSM,WCDMA, LTE, CDMA2000 network). The wireless transceiver 1106 may beconfigured to receive various radio frequency (RF) signals (e.g., signal1110) via antenna 1108, respectively, from one or more other accesspoints, network devices, beacons and/or the like. Access point 1100 mayalso be configured to decode and/or decrypt various signals receivedfrom one or more access points, network devices, wireless clientdevices, and/or the like.

The access point 1100 may include a power supply (not shown) that canpower the various components. The power supply may include aswitched-mode power supply, a linear power supply, a push-pull powersupply, or any other suitable type of power supply. In some embodiments,the access point 1100 may include multiple power supplies. For example,a switched-mode power supply may be used to condition input power, and alinear power supply may be used to power the RF circuit. The powersupply may be configured to operate over various ranges of appropriateinput voltages.

Alternatively, the access point 1100 may include circuitry for receivingvoltage, current or power via an external power supply or a Power overEthernet connection. Power over Ethernet support is optionally providedby network interface 1120. Network interface 1120 can provide fornetwork connections to external devices via any standardized orspecialized network connection, such as IEEE 802.3. In an exemplaryembodiment, network interface 1120 provides support for a wired Ethernetconnection to a network. Other wired network technologies arecontemplated for connection to networks, as will be understood by theskilled artisan; however, due to its ubiquitous nature and support forPower over Ethernet, wired Ethernet over twisted pairs may bepreferentially employed.

The access point 1100 may further include (and/or be in communicationwith) one or more non-transitory machine-readable storage mediums orstorage devices (e.g., memory 1112), which can comprise, withoutlimitation, local and/or network accessible storage, and/or can include,without limitation, a disk drive, a drive array, an optical storagedevice, a solid-state storage device such as a random access memory(“RAM”) and/or a read-only memory (“ROM”), which can be programmable,flash-updateable and/or the like. Such storage devices may be configuredto implement an appropriate data storage, including without limitation,various file systems, database structures, and/or the like.

In various embodiments, functions may be stored as one or morecomputer-program products, such as instructions or code, in memory 1112,such as RAM, ROM, FLASH, or disc drive, and executed by processor(s)1102. The access point 1100 can also comprise software elements (e.g.,located within the memory 1112), including, for example, an operatingsystem, device drivers, executable libraries, and/or other code, such asone or more application programs, which may comprise computer programsimplementing the functions provided by various embodiments, and/or maybe designed to implement methods and/or configure systems, as describedherein.

FIG. 12 illustrates an example of a server 1200. In various embodiments,server 1200 may communicate with other devices such as using one or morewireless or wired data networks. Server 1200 may provide networkservices and/or may be used to control and/or manage one or morewireless devices, such as one or more wireless access points. The server1200 includes hardware elements that can be electrically coupled via abus 1218 (or may otherwise be in communication, as appropriate). In oneembodiment, the bus 1218 can be used for the processor(s) 1202 tocommunicate between cores and/or with the memory 1212. The hardwareelements may include one or more processors 1202, including withoutlimitation one or more general-purpose processors and/or one or morespecial-purpose processors (such as digital signal processing chips,graphics acceleration processors, and/or the like), memory 1212, outputdevices 1214, input devices 1216, a bus 1218 and a network interface1220. Furthermore, in addition to the network interface 1220, server1200 can optionally further include a wireless transceiver tocommunicate with a network (e.g., a wireless local area network, awireless network of a preferred carrier, Internet, etc.).

The server 1200 may further include (and/or be in communication with)one or more non-transitory machine-readable storage mediums or storagedevices (e.g., memory 1212), which can comprise, without limitation,local and/or network accessible storage, and/or can include, withoutlimitation, a disk drive, a drive array, an optical storage device, asolid-state storage device such as a random access memory (“RAM”) and/ora read-only memory (“ROM”), which can be programmable, flash-updateableand/or the like. Such storage devices may be configured to implement anyappropriate data storage, including without limitation, various filesystems, database structures, and/or the like.

In various embodiments, functions may be stored as one or more one ormore computer-program products, such as instructions or code, in memory1212. The server 1200 can also comprise software elements (e.g., locatedwithin the memory), including, for example, an operating system, devicedrivers, executable libraries, and/or other code, such as one or moreapplication programs, which may comprise computer programs implementingthe functions provided by various embodiments, and/or may be designed toimplement methods and/or configure systems, as described herein. Merelyby way of example, one or more procedures described with respect to theprocesses discussed above may be implemented as code and/or instructionsexecutable by a computer (and/or a processor within a computer); in anaspect, then, such code and/or instructions can be used to configureand/or adapt a general purpose computer (or other device) to perform oneor more operations in accordance with the described methods. Suchfunctions or code may include code to perform the aspects of methodsdescribed herein, such as centralized management and control overwireless access points, beacons, etc. The memory 1212 may be anon-transitory machine-readable storage medium, processor-readablememory, and/or a computer-readable memory that stores the one or morecomputer-program products configured to cause the processor(s) 1202 toperform the functions described. In other embodiments, one or more ofthe functions described may be performed in hardware.

A set of these instructions and/or code is optionally stored on anon-transitory machine-readable storage medium, such as the memory 1212.In some cases, the storage medium is optionally incorporated within acomputer system. In other embodiments, the storage medium is optionallyseparate from a computer system (e.g., a removable medium, such as acompact disc), and/or provided in an installation package, such that thestorage medium can be used to program, configure and/or adapt a generalpurpose computer with the instructions/code stored thereon. Theseinstructions of one or more computer-program products might take theform of executable code, which is executable by the server 1200 and/ormay take the form of source and/or installable code, which, uponcompilation and/or installation on the server 1200 (e.g., using any of avariety of generally available compilers, installation programs,compression/decompression utilities, etc.) then takes the form ofexecutable code.

Merely by way of example, one or more procedures described with respectto the processes or methods discussed above, for example as describedwith respect to FIG. 5-9 or any portion thereof, may be implemented ascode and/or instructions executable by a computer or device (and/or aprocessor within a computer or device); in an aspect, then, such codeand/or instructions can be used to configure and/or adapt a generalpurpose computer (or other device) to perform one or more operations inaccordance with the described methods. Such functions or code mayinclude code to perform the steps described above with respect to FIGS.5-9 and portions thereof. The memory may be a non-transitorymachine-readable storage medium, processor-readable memory, and/or acomputer-readable memory that stores the one or more computer-programproducts configured to cause the processor(s) to perform the functionsdescribed. In other embodiments, one or more of the functions describedmay be performed in hardware. Aspects of the disclosed methods, whenperformed by a general purpose computer, allow the general purposecomputer to perform more efficiently, such as by performing an operationin fewer steps or using less memory or processing time, than priormethods. Further, performance of aspects of the disclosed methods by ageneral purpose computer may transform the general purpose computer intoa special purpose computer, such as a network device, a wireless accesspoint, a wireless client, etc. Aspects of the disclosed methods, whenperformed by a general purpose computer, further allow the generalpurpose computer to perform new functions and/or to perform functions innew ways, such as in more useful orders. For example, aspects of thedisclosed methods achieve simplified and/or more efficient operation ofnetwork devices, such as client devices and wireless access point, aswell as efficiency gains in operation of wireless networking and use ofthe radio frequency medium.

A set of these instructions and/or code might be stored on anon-transitory machine-readable storage medium, such as the memory. Insome cases, the storage medium might be incorporated within a computersystem. In other embodiments, the storage medium might be separate froma computer system (e.g., a removable medium, such as a compact disc),and/or provided in an installation package, such that the storage mediumcan be used to program, configure and/or adapt a general purposecomputer with the instructions/code stored thereon. These instructionsof one or more computer-program products might take the form ofexecutable code, which is executable by a computer or device and/ormight take the form of source and/or installable code, which, uponcompilation and/or installation on the computer or device (e.g., usingany of a variety of generally available compilers, installationprograms, compression/decompression utilities, etc.) then takes the formof executable code.

Substantial variations may be made in accordance with specificrequirements. For example, customized hardware might also be used,and/or particular elements might be implemented in hardware, software(including portable software, such as applets, etc.), or both. Further,connection to other access or computing devices such as networkinput/output devices may be employed.

In the foregoing specification, aspects of the invention are describedwith reference to specific embodiments thereof, but those skilled in theart will recognize that the invention is not limited thereto. Variousfeatures and aspects of the above-described invention may be usedindividually or jointly. Further, embodiments can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive.

In the foregoing description, for the purposes of illustration, methodswere described in a particular order. It should be appreciated that inalternate embodiments, the methods may be performed in a different orderthan that described. It should also be appreciated that the methodsdescribed above may be performed by hardware components or may beembodied in sequences of machine-executable instructions, which may beused to cause a machine, such as a general-purpose or special-purposeprocessor or logic circuits programmed with the instructions to performthe methods. These machine-executable instructions may be stored on oneor more machine readable mediums, such as CD-ROMs or other type ofoptical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magneticor optical cards, flash memory, or other types of machine-readablemediums suitable for storing electronic instructions. Alternatively, themethods may be performed by a combination of hardware and software.

Where components are described as being configured to perform certainoperations, such configuration can be accomplished, for example, bydesigning electronic circuits or other hardware to perform theoperation, by programming programmable electronic circuits (e.g.,microprocessors, or other suitable electronic circuits) to perform theoperation, or any combination thereof.

While illustrative embodiments of the application have been described indetail herein, it is to be understood that the inventive concepts may beotherwise variously embodied and employed, and that the appended claimsare intended to be construed to include such variations, except aslimited by the prior art.

What is claimed is:
 1. A method, comprising: transmitting, by a device,a frame comprising a media access control (MAC) address corresponding tothe device to a network device; receiving, by the device, a responsefrom the network device, wherein the response comprises a designated MACaddress; transmitting, by the device, an association request to thenetwork device, wherein the association request comprises the designatedMAC address that is included and updated in an entry for the device inan association table stored at the network device; and receiving, by thedevice, an association response from the network device, wherein theassociation response comprises an association identifier.
 2. The methodof claim 1, wherein the network device further updates the associationtable with the entry for the device using the designated MAC address. 3.The method of claim 1, further comprising: receiving an indicator of anavailability of designated MAC addresses.
 4. The method of claim 3,further comprising: transmitting a request for a designated MAC addressto the network device, wherein the network device identifies adesignated MAC address in response to receiving the request.
 5. Themethod of claim 3, wherein receiving the indicator includes receiving abeacon frame or a probe response frame, and wherein the beacon frame orprobe response frame includes the indicator.
 6. The method of claim 3,wherein a service set identifier (SSID) of the beacon frame or proberesponse frame includes the indicator.
 7. The method of claim 1, furthercomprising: displaying a captive portal website, wherein the captiveportal website requests input authorizing use of a designated MACaddress; receiving input corresponding to an authorization to use thedesignated MAC address; and transmitting the authorization.
 8. Themethod of claim 1, further comprising: receiving an association query,wherein the association query includes the designated MAC address; andtransmitting a response to the association query.
 9. The method of claim1, wherein the network device is a wireless access point compliant withan IEEE 802.11 standard.
 10. The method of claim 1, wherein the responsecomprises a pool of MAC addresses.
 11. The method of claim 1, whereinthe association request comprises a dynamic host configuration protocol(DHCP) message.
 12. A non-transitory computer readable medium comprisinginstructions that, when executed by at least one processor of a device,cause the at least one processor to perform operations including:transmitting a frame comprising a media access control (MAC) addresscorresponding to the device to a network device; receiving a responsefrom the network device, wherein the response comprises a designated MACaddress; transmitting an association request to the network device,wherein the association request comprises the designated MAC addressthat is included and updated in an entry for the device in anassociation table stored at the network device; and receiving anassociation response from the network device, wherein the associationresponse comprises an association identifier.
 13. The non-transitorycomputer readable medium of claim 12, wherein the network device furtherconfirms that the designated MAC address included in the associationrequest is authorized for use by the wireless device.
 14. Thenon-transitory computer readable medium of claim 12, wherein theoperations further comprising: receiving an association query, whereinthe association query includes the designated MAC address; andtransmitting a response to the association query; receiving anauthentication query; and transmitting a response to the authenticationquery.
 15. The non-transitory computer readable medium of claim 12,wherein the response comprises a pool of MAC addresses.
 16. Thenon-transitory computer readable medium of claim 12, wherein theassociation request comprises a dynamic host configuration protocol(DHCP) message.
 17. A device, comprising: a processor; and a memorystoring instructions which, when executed cause the device to performoperations including: transmitting, a frame comprising a media accesscontrol (MAC) address corresponding to the device to a network device;receiving a response from the network device, wherein the responsecomprises a designated MAC address; transmitting an association requestto the network device, wherein the association request comprises thedesignated MAC address that is included and updated in an entry for thedevice in an association table stored at the network device; andreceiving an association response from the network device, wherein theassociation response comprises an association identifier.
 18. The deviceof claim 17, wherein the network device further confirms that thedesignated MAC address included in the association request is authorizedfor use by the wireless device.
 19. The device of claim 17, wherein theresponse comprises a pool of MAC addresses.
 20. The device of claim 17,wherein the association request comprises a dynamic host configurationprotocol (DHCP) message.